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.
SLA timers are wrongly firing breach emails - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • SLA timers are wrongly firing breach emails
KB0695958

SLA timers are wrongly firing breach emails


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

Issue

Symptoms


Receiving unexpected SLA breach emails

Release


Jakarta Patch 8a

Cause


What the user is seeing is expected behavior based on their configuration (please see continued explanation below...)

Resolution


Per the above, the behavior seen is expected as the workflow associated to the task_sla record does not recognize schedules on SLA definitions. Rather, the "SLA Percentage Timer" activity counts up to 100 percent based on when the task_sla attaches to the parent record.

When an SLA is attached, the workflow associated to the definition begins running immediately.

The task_sla of concern, "Change SLA - 8 Hours" attached to the parent record on 2018-07-31 at 09:59:22.

The duration set on the relevant SLA Definition is 8 hours.

Therefore, based on this information, an e-mail notification should fire per the SLA breaching on 2018-07-31 at about 17:59:22 (roughly 8 hours later).

Indeed, the notification did fire: "CHG0642119 has exceeded closure SLA" at 2018-07-31, 17:59:31.

This is expected.

To avoid this behavior in the future, modify the workflow.

After the "Begin" activity, it is recommended to use a "Wait For" activity with a Script inside which tells the system to calculate based on the Planned End Time (the user's desired "start" time). Only when that "start" time is reached, begin the 100% countdown.

In this way, the above behavior will be avoided.


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.