Q: What causes SLA Pausing Unexpectedly in ServiceNow?

Pause condition matches transient record states — Navigate to System Definition > SLA Definitions and check the 'Pause condition' field on your SLA. Look for conditions that trigger on temporary states like 'On Hold', 'Pending', or workflow states that the record may enter briefly during processing. SLA schedule excludes current time period — Check the 'Schedule' field on your SLA Definition and verify the associated schedule in System Definition > Schedules. The SLA appears paused during excluded hours but is actually following the schedule correctly. Business Rule manually manipulating task_sla state — Search System Definition > Business Rules for rules that run on your task table or the task_sla table. Look for scripts that set 'pause_time', 'pause_duration', or call pauseSLA() methods on task_sla records. Retroactive start setting affecting SLA calculation — Check the 'Retroactive start' checkbox on your SLA Definition. When enabled, this recalculates the SLA timeline based on the actual start condition timing, which can create apparent pause/resume behavior. Multiple SLA conditions triggering simultaneously — Review the 'Start condition' and 'Stop condition' fields on your SLA Definition for overlapping logic. Check if workflow or field changes are causing the SLA to stop and restart, appearing as pause behavior.

Question 1

What causes SLA Pausing Unexpectedly in ServiceNow?

Accepted Answer

Pause condition matches transient record stateshigh likelihood

Navigate to System Definition > SLA Definitions and check the 'Pause condition' field on your SLA. Look for conditions that trigger on temporary states like 'On Hold', 'Pending', or workflow states that the record may enter briefly during processing.

SLA schedule excludes current time periodhigh likelihood

Check the 'Schedule' field on your SLA Definition and verify the associated schedule in System Definition > Schedules. The SLA appears paused during excluded hours but is actually following the schedule correctly.

Business Rule manually manipulating task_sla statemedium likelihood

Search System Definition > Business Rules for rules that run on your task table or the task_sla table. Look for scripts that set 'pause_time', 'pause_duration', or call pauseSLA() methods on task_sla records.

Retroactive start setting affecting SLA calculationmedium likelihood

Check the 'Retroactive start' checkbox on your SLA Definition. When enabled, this recalculates the SLA timeline based on the actual start condition timing, which can create apparent pause/resume behavior.

Multiple SLA conditions triggering simultaneouslylow likelihood

Review the 'Start condition' and 'Stop condition' fields on your SLA Definition for overlapping logic. Check if workflow or field changes are causing the SLA to stop and restart, appearing as pause behavior.

Question 2

How do you fix SLA Pausing Unexpectedly in ServiceNow?

Accepted Answer

How to fix it Navigate to System Definition > SLA Definitions and open the problematic SLA definition. Examine the Pause condition field. If it references states like 'On Hold', 'Pending', or workflow states, verify these aren't being triggered by automated processes or user actions. Open the specific task record experiencing SLA issues and check System Logs > SLA Debug Log for pause/resume entries that correlate with field changes. If pause conditions are too broad, modify them to be more specific. Replace conditions like state=6 with compound conditions that include additional criteria to avoid transient state matching. Check the Schedule field on the SLA definition. Navigate to System Definition > Schedules and verify the associated schedule covers the expected business hours. In the task record, check if you're viewing Business elapsed time vs Elapsed time. Business elapsed time excludes non-business hours per the schedule, which may appear as pausing. Search System Definition > Business Rules for rules running on your task table (incident, change, etc.) or the task_sla table. Review Business Rule scripts for SLA manipulation methods like pauseSLA(), resumeSLA(), or direct field updates to pause_time or pause_duration. If you find problematic Business Rules, add logging to track when and why they're executing, then modify the conditions to prevent unintended SLA manipulation. Check the Retroactive start checkbox on the SLA definition. If enabled, disable it temporarily to see if the apparent pausing behavior resolves. Navigate to the task record and go to Related Links > SLA Details to view the complete SLA timeline with pause/resume events and their timestamps. Cross-reference pause/resume timestamps with the task's Activity Log to identify which field changes or actions triggered the SLA state changes.

Question 3

How do you prevent SLA Pausing Unexpectedly in ServiceNow?

Accepted Answer

Always test SLA pause conditions in a development instance by creating test records that go through all possible state transitions to identify unintended pause triggers. Document all custom Business Rules that interact with SLA records and include comments explaining why SLA manipulation is necessary to prevent future confusion. Set up SLA debugging by enabling 'Debug SLA' in System Properties > Service Level Management before deploying new SLA definitions to production. Create SLA pause conditions that require multiple field criteria rather than single field values to avoid matching transient states during record processing. Establish a naming convention for SLA schedules that clearly indicates business hours coverage and regularly audit schedules to ensure they match current business requirements.

SLA Pausing Unexpectedly in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge