Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Excessive 'ASYNC: Handle User-Activation CT tracking' jobs when sys_user table is updated - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Excessive 'ASYNC: Handle User-Activation CT tracking' jobs when sys_user table is updated
KB0789233

Excessive 'ASYNC: Handle User-Activation CT tracking' jobs when sys_user table is updated


491 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

The system has millions of records with a next action date in the past. Most of the records appear to be (ASYNC: Handle User-Activation CT Tracking). This backup is causing a delay with our other jobs.

Similar to KB0789201/PRB1374288 except the name has an ending 'g'  '

ASYNC: Handle User-Activation CT Tracking <> ASYNC: Handle User-Activation CT Trackin

Release

Madrid P7a

Cause

  1. The high volume of ASYNC: Handle User-Activation CT Tracking jobs comes from the Business Rule Handle User-Activation CT Tracking which comes from this functionality: Using Subscription Management to Monitor Usage
  2. The Business Rule Handle User-Activation CT Tracking activates when any update is made on the sys_user table
  3. Imports that are making a lot of updates to the sys_user table will cause this issue.
  4. This is related to PRB1374288 but with a slightly different symptom.

Resolution

You can delete all of the pending ASYNC: Handle User-Activation CT Tracking jobs so it does not delay your other jobs from running

For preventive measure, you can do either of the following:

  1. Disable business rules to run when running the imports to the sys_user table
    • OR
  2. Add a condition on the business rule Handle User-Activation CT Tracking to not execute the update comes from an import (maybe by the user who is making the update to sys_user)
    • OR
  3. Disable the business rule Handle User-Activation CT Tracking if you're not using it.

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.