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.
Determine if there was an exception that prevents workflow from starting or resuming - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Determine if there was an exception that prevents workflow from starting or resuming
KB0538284

Determine if there was an exception that prevents workflow from starting or resuming


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

Issue

Determine if there was an exception that prevents workflow from starting or resuming 
 

Symptoms

Symptoms may include the following:
  • Workflow did not run when expected
  • Workflow did not run on a specific record
  • Workflow not attaching
  • Workflow not progressing to the next activity
  • Cannot publish workflow
  • Publishing workflow takes too long
  • Cannot start workflow
  • Workflow does not trigger
  • Stalled workflow   
Cause
In most cases, the problem is due to an exception during the transaction following the workflow activity. Updating the record that the workflow is attached to starts or resumes the workflow. 
How to locate the exception in the logs
Look in the logs on both nodes and determine the node on which the transaction happened. Go to the Log File Download and locate the date on which the tranaction happened and download the logs from that day on both nodes.

  1. Locate the exact time at which the transaction occured and check to see if there were any transactions that caused any exceptions.
  2. In most cases, Null Pointer Exception is the cause of a cancelled transaction, which will prevent the update of the business rule that triggers the workflow to continue.
  3. Once the exception is located, continue to investigate the cause of the exception and how to prevent the exception. This can be done by tracing the stack trace of the exception and locating where this happened.  

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.