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.
The same SLA Definition is not attaching as a task SLA in all instances even when conditions are met - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • The same SLA Definition is not attaching as a task SLA in all instances even when conditions are met
KB0829003

The same SLA Definition is not attaching as a task SLA in all instances even when conditions are met


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

Issue

The user was experiencing an issue where SLA Definition "Apple" was attaching just fine in their Dev and Test instances, but the same SLA Definition was not attaching (even when the Start conditions were matching) in their UAT instance. They wanted to know why this was.

Resolution

Every so often when a SLA Definition is moved from one instance to another, an issue can occur where the definition does not completely insert into the back-end. 

Unfortunately, the only symptom of this behavior is that the user will take note that even when the Start conditions are met, the SLA Definition does not attach as a task SLA - ever. If the SLA Definition does attach, even intermittently, the user can be sure that this is not the incomplete insert issue.

A good test to see that the user is facing this specific behavior is to do an insert and stay on the affected SLA Definition(s), making some prefix to the name of the SLA to distinguish it from the defunct original. If upon creating a test record the insert-and-stay version of the SLA Definition attaches as a task SLA, the user can be sure that they are facing this incomplete insert issue.

To resolve the behavior, then, the user should navigate to the affected SLA Definition(s), export them to XML, and re-import them. A simple second test record will prove that the behavior has been resolved if the original SLA Definition and the insert-and-stay version of the SLA Definition both attach. The insert-and-stay version of the SLA Definition can then be removed.


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.