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 legacy SLA 2010 engine does not attach a Task SLA to task record when start and stop conditions are both met for an SLA at the same time - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • The legacy SLA 2010 engine does not attach a Task SLA to task record when start and stop conditions are both met for an SLA at the same time
KB0622993

The legacy SLA 2010 engine does not attach a Task SLA to task record when start and stop conditions are both met for an SLA at the same time


1697 Views Last updated : Jan 28, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Task records do not trigger SLAs if the SLAs Start and Stop conditions are met at the same time. In this case, the Task SLA is never created.

Steps to Reproduce

- Login to any ServiceNow instance using the legacy 2010 SLA engine
- Import the attached 'P5-SameStartandStopCondition' SLA definition
- Create a new incident and set the priority to 5 and Assignment Group as 'Database'
- Observe that no Task SLA is created because the SLAs Stop condition of 'State=New' is immediately met
- Edit the SLA to make the stop condition something else other than New and try it again by marking the new incident resolved and it will attach the sla.

Workaround

The generation of Task SLA records when both Start and Stop match occurs only using the 2011 SLA engine. This is available on all Enterprise instances, but not on Express instances, which are instead based on the legacy 2010 engine.

SLA condition rules

Legacy SLA engines

In Enterprise, for the SLA that should always attach, use the Simple condition type on that SLA Definition. The only caveat is that Cancel and Resume conditions cannot be used when using the Simple condition type. If Cancel and Resume must be used then we recommend creating a new script include that extends SLAConditionBase that then overrides the attach method (using the contents of the attach method from SLAConditionSimple).

For Express, please refer to the documentation below:

Service level agreements (SLAs)

Understanding SLA measurements in Express

How the SLA engine works in Express – your FAQs answered

 


Related Problem: PRB724111

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.