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.
When worknotes are added to an incident, task_slas are being duplicated - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • When worknotes are added to an incident, task_slas are being duplicated
KB0814942

When worknotes are added to an incident, task_slas are being duplicated


765 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

The user is facing an issue where when they are adding a work note to an incident, the associated task_slas on that incident are being duplicated. They wanted to know why.

Resolution

The cause for the behavior is that there are conflicting conditions on the SLA Definition along with the use of the "Simple" Condition type.

The example incident INC0010000 has a state of "Pending" and is still active.

When adding a work note to the incident, the start condition on SLA Definition "INC Response - 15 Min" is met because the incident's state is not Resolved or Closed. Thus, a new Task SLA is attached (because the user has configured their SLA Definition to use the "Simple" condition type, the system does not test if the stop condition matches).

Now, when SLA processing processes the existing Task SLAs it finds the one just created and so tests for pause/stop/cancel. Stop condition matches as this checks for State is Resolved or is not New, thus the Task SLA gets instantly marked as completed.

The simplest fix for this issue is to set the Condition type back to "Default", which is the Out of Box (OOB) value. Once that change was made, task_slas no longer duplicated.


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.