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.
Workflow timer intermittently waits longer than timer is set for - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Workflow timer intermittently waits longer than timer is set for
KB0814939

Workflow timer intermittently waits longer than timer is set for


921 Views Last updated : Sep 21, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Workflow set on the sc_request table seems to hang intermittently on the first-timer of 10's.

Managed to get it started by updating the REQ itself, the restart hung workflow did not work.

Release

ALL

Cause

ASYNC Business Rules

Resolution

- The system does not allow the WFTimer jobs to be pushed ahead of ASYNC jobs, and vice-versa. This causes delay in WFTimer jobs while waiting on the worker threads.
- Open the System Diagnostics page and check the scheduler queue length. In these circumstances, if the value shows in red, the scheduler is overloaded. Check all active ASYNC Business Rules generating scheduled jobs that are flooding the scheduler. Disable Async Business Rules, review and evaluate why the scheduler cannot handle the intended load.
- For the priority level issue of the timer activity, a business rule can be created on the sys trigger table that will check to see if a wf.timer record is inserted. Once it gets inserted, the business rule should change the priority value to 90.
- All jobs on the sys_trigger table run at a priority 100. Therefore, making the wf.timer priority to 90 will cause it to run before other scheduled jobs, which will fix the issue.



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.