How to Fix Random SLA Timer Pauses in Dynamics 365 Customer Service
A troubleshooting guide to the real causes behind SLA KPI timers that pause without warning, and how to stop the false breach alerts they trigger.
Random SLA timer pauses in Dynamics 365 Customer Service almost always come down to a handful of causes: pause-and-resume status rules, business-hours calendars, background workflows or Power Automate flows, and custom plugins that update the case. This guide walks through how to find which one is at play and how to fix it, so you stop getting false breach alerts and your agents' SLA KPIs stay accurate. Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy that rescues and optimizes broken Customer Service implementations, and these are the same checks we run on real client environments.
Common causes of random SLA timer pauses
Pause-and-resume status rules
The single most common cause. In Customer Service admin (Service Configuration Settings, "Pause and resume SLA on status"), you nominate one or more case statuses, typically "On Hold" and "Waiting for Details", that pause every active SLA KPI. Any process that moves a case into one of those statuses will stop the timer. If a status is on that pause list unintentionally, timers look like they stop at random.
Business hours / customer service calendar
An SLA KPI can be calculated against a customer service schedule (business hours). Outside working hours the timer legitimately pauses. A calendar with the wrong working days, wrong time zone, or holiday schedule attached to the SLA makes those pauses appear arbitrary to anyone reading the clock in a different time zone.
Background workflows and Power Automate flows
A classic workflow or a Power Automate cloud flow that updates the case, for example flipping the status reason to an on-hold value when an email arrives, or on assignment, will pause the SLA as a side effect. Because these run asynchronously, the pause can land seconds after an agent's action and feel disconnected from it.
Custom plugins on Update of the case
A registered plugin or custom API that writes to the case state, status reason, or an SLA-related field during Update can pause or reset the KPI. Plugins firing on a shared message (e.g. Update of incident) are easy to overlook when auditing SLA behaviour.
Enhanced SLA condition and KPI configuration
With Enhanced SLAs, each SLA item has Applicable When, Success, Pause, and Warning/Failure conditions plus its own KPI. A mismatch between the applicable-when and pause conditions, or overlapping SLA items competing on the same case, can produce a timer that starts, pauses, and resumes in ways that look random until the conditions are read carefully.
Step-by-step: diagnose and fix the pauses
Work through these in order. Each step narrows down the cause; steps 5 to 7 apply and validate the fix.
Confirm which SLA is active and its type
Open the affected case and check the Enhanced SLA Details (timeline / SLA KPI Instances) or the case's SLA field. Identify whether you are on a Standard or Enhanced SLA and exactly which SLA record and KPI applies. Random-looking behaviour is often two different SLAs or KPIs acting on the same case.
Review the pause-and-resume status configuration
In the Customer Service admin center, open Service Configuration Settings and inspect "Pause and resume SLA on status." Note every status reason that pauses SLAs. If a status is on this list that agents move cases into during normal work, the timer will pause every time, so remove statuses that should not pause the clock.
Audit the case status-reason transitions
Enable and read auditing on the incident (case) entity for the status and status reason fields. Walk the audit history of an affected case to see exactly when it entered a paused status and what made that change, whether a user, a workflow, a flow, or a plugin. This pinpoints the trigger instead of guessing.
Verify the business-hours calendar and time zone
Open the customer service schedule attached to the SLA (or SLA KPI) and confirm the working days, working hours, holiday schedule, and time zone. Compare them against where your agents and customers actually are. Correct any mismatched time zone or schedule so out-of-hours pauses stop looking random.
Inspect background workflows, flows, and plugins
Review real-time and background workflows, Power Automate cloud flows, and registered plugins/custom APIs that trigger on Update or status change of the case. Look for any that set the status reason to a paused value or write to SLA fields. Temporarily deactivate suspects in a sandbox to confirm which one moves the timer.
Examine the SLA KPI Instance records
Query the SLA KPI Instance records for affected cases and read the failure time, warning time, pause/resume timestamps, and status. Stuck, duplicated, or unexpectedly paused instances confirm the SLA engine itself is behaving as configured, and show whether a re-apply of the SLA is required.
Reproduce, fix, and validate in a sandbox
Reproduce the pause in a non-production environment, apply the fix, such as correcting the pause list, fixing the calendar, or adjusting the offending workflow/flow/plugin, and confirm the KPI now runs and breaches as expected. Only then promote the change to production and re-apply the SLA to open cases if needed.
Frequently Asked Questions
Why does my Dynamics 365 SLA timer pause randomly?
The most common reason is that the case has entered a status that is on the "Pause and resume SLA" list in Service Configuration Settings, often "On Hold", usually set by an agent, a background workflow, a Power Automate flow, or a plugin. Business-hours calendars and time-zone mismatches are the next most common cause. Auditing the status-reason changes on an affected case almost always reveals the trigger.
How do I stop false SLA breach and pause alerts for my agents?
Remove any status from the pause-and-resume list that agents move cases into during normal handling, align the SLA's customer service schedule and time zone with where your agents work, and fix any workflow, flow, or plugin that changes the case status as a side effect. Then re-apply the SLA to affected cases so the KPI recalculates correctly.
Does a business-hours calendar cause SLA timers to pause?
Yes. When an SLA KPI is calculated against a customer service schedule, the timer legitimately pauses outside working hours and on holidays. If the calendar has the wrong time zone or working days, those pauses look random to anyone reading the clock elsewhere. Check the schedule attached to the SLA or KPI first.
Can a Power Automate flow or plugin pause an SLA timer?
Indirectly, yes. SLA timers do not have a direct "pause" action, but any workflow, Power Automate flow, or plugin that updates the case status to a value on the pause list will pause every active SLA KPI. Because these run in the background, the pause can appear seconds after an unrelated action and feel random.
Can Solzet fix a broken Dynamics 365 Customer Service SLA setup?
Yes. Solzet is a Microsoft Dynamics 365 Customer Engagement and Power Platform consultancy based in Yerevan, Armenia, with MB-230 (Customer Service) certified consultants. We run exactly these diagnostics on client environments as part of our project rescue and optimization work, then correct the SLA, calendar, workflow, and plugin configuration and validate it in a sandbox before go-live.
SLAs still misbehaving? We rescue them.
Solzet's MB-230 certified Dynamics 365 Customer Service consultants run these exact diagnostics as part of our project rescue and optimization work. Tell us what your timers are doing and we'll fix the configuration behind them.