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.
Incident is closed but does not show this in the activity log or audit history. As a result, SLAs are not working as expected. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Incident is closed but does not show this in the activity log or audit history. As a result, SLAs are not working as expected.
KB0695960

Incident is closed but does not show this in the activity log or audit history. As a result, SLAs are not working as expected.


1598 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


The incident record is closed, but this state transition is not showing in the activity log or audit history. As a result, relevant SLAs are not transitioning stage and are still showing as "Paused" (when they should be "Completed")

Release


Jakarta Patch 7

Cause


Two after Business Rules with the name execution Order are why this intermittent behavior is happening (depending on which of the two runs first).

Resolution


The user has the following after Business Rules running:

  • incident autoclose
  • Create Problem when state is Resolved


Both of these after Business Rules have an execution Order of 100. This is the issue, and why this behavior is intermittent.

Looking at INC0010000, the incident was moved to a state of "Resolved" at 2018-07-13 22:11:47 by James.

Similarly, per the user's Business Rule "Create Problem when state is Resolved", PRB0010000 was opened at 2018-07-13 22:11:47 (the same time).

Unfortunately, within Business Rule "Create Problem when state is Resolved", the user has the following snippet of code: current.setWorkflow(false); This is not bad in-and-of itself. It is only causing an issue because the two Business Rules are racing to see which one will execute first (again, hence the inconsistency of the behavior).

The above piece of code will prohibit all Business Rules from executing after it runs (in this case, it prevented "incident autoclose" from running), which is why the moving of State to "Closed" was never tracked, and thus, never passed down to the task_sla records to progress them to a "Completed" stage.

Again, the issue here is that both of these Business Rules, "Create Problem when state is Resolved" and "incident autoclose" are executing on the same Order # (100). 

Suggest that the user modify their "Create Problem when state is Resolved" to execute on a higher order number than "incident autoclose".

Making the above modification will ensure that the "incident autoclose" Business Rule runs first and succesfully passes down that closure to the task_sla records, resolving this intermittent SLA behavior. Then, the PRBs will be safely created after "incident autoclose" has already run.


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.