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.
Intermittently the workflow does not run even though the conditions are met - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Intermittently the workflow does not run even though the conditions are met
KB0826287

Intermittently the workflow does not run even though the conditions are met


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

Issue

  • Intermittently the workflow does not run even though the conditions are met
  • Workflows on record insert are not triggered

STEPS TO REPRODUCE:

  1. Create a workflow on [incident] table
  2. With the following conditions:
    • short description "start with" "abcdef"
    • assignment group "is" "Software"
  3. Enable OOB assignment rule "Database or Software"
  4. create an incident record, where the short description is "abcdef" and set the category to "software"
  5. notice that the newly created incident, the short description is "abcdef" and assignment group is "software"

UNEXPECTED BEHAVIOR:
intermittently the workflow we created does not launch

EXPECTED BEHAVIOR:
the workflow should launch all the time

Cause

  • both the workflow engine and the assignment engine are Before engines.
  • and based on the documentation "are not executed in any specific order"
  • So this means that the workflow engine might evaluate the task record before the assignment rule assigns the group to the task
  • and this is why the workflow is not firing

Resolution

  • you can do is defer the workflow after the DB operation.
  • You can do that by checking off the "Run after bus. rules run" field on the workflow's properties (see image below).

 


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.