The SLA That Looks Met but Isn’t
A customer service team in 2026 reported 96% SLA compliance for the quarter. Internal QA pulled a sample of 50 cases marked “met” and found 11 where the SLA had paused mid-resolution and never resumed. The dashboard counted them as met because the timer was paused at “well within target.” The customers waited an additional 38 hours on average. Nobody saw it because the metric reported what it was told.
That gap is the SLA Pause vs Stop design problem. In Dynamics 365 Customer Service, the two states look almost identical in the UI and the report — and they behave very differently. The 2026 Wave 1 release added more granular pause conditions, which made the trap worse because the rules grew in number without growing in visibility.
What Pause and Stop Actually Do
Pause suspends the SLA timer. The KPI instance stays “In Progress,” the timer holds at its current elapsed time, and when a defined condition flips, the timer resumes. Pause is reversible. Pause is the right tool for “waiting on customer” or “external dependency.”
Stop terminates the SLA timer. The KPI instance moves to “Succeeded” or “Cancelled.” There is no resume. Stop is the right tool for “case is resolved” or “scope changed and a new SLA applies.”
The mistake teams make is using Pause when they should be using Stop, or configuring a Pause condition that depends on a field state nobody changes back. The timer pauses on “Status = On Hold.” The case sits On Hold while waiting for procurement. Procurement closes the loop, the agent forgets to flip status back to Active, and the case eventually resolves with status still On Hold. The KPI never resumed; the SLA reports as paused, then as met when the case closes.
The Two Conditions to Audit Right Now
In the SLA admin area, every active SLA item has both a “Pause Configuration” and an “Applicable When” condition. The audit is:
- Pause Configuration: Is the resume condition the inverse of the pause condition? If you pause on “Status = On Hold,” your resume needs to fire on “Status changed from On Hold to anything else.” If it’s a more permissive condition (“Status = Active”), and the agent skips Active and goes straight to Resolved, the resume never fires.
- Applicable When: Does the SLA stop applying when status enters Resolved/Closed? If not, you can have an “in progress” KPI on a closed case — invisible until you query it directly.
Pull the Power Automate flow history for the SLA service’s audit trail and search for KPI instances with Status = InProgress AND IncidentStatus IN (Resolved, Cancelled). Every match is a silent miss.
The Cleaner Design
The pattern that survives auditing has three rules:
1. Pause only on conditions that auto-reverse. “Customer last responded > 24 hours ago” is a good pause condition because time fixes it. “On Hold for Procurement” is a bad pause condition because it depends on a human action that may not happen.
2. Add a maximum pause duration. Configure a Power Automate flow that wakes daily and re-evaluates any KPI instance in “Paused” state for more than 7 days. If it’s still paused, flip the case to a “Stalled” sub-status and notify the case owner. The pause has a leash.
3. Don’t pause for “scope changed” — stop and restart. When a customer escalates a case to enterprise tier, the original SLA’s target no longer fits. Don’t pause it. Stop it as “Cancelled, scope change” and start a new SLA instance with the new tier. Reports stay clean. Compliance math stays honest.
What 2026 Wave 1 Changed (and the Sharp Edge)
Wave 1 added support for pausing on AI-derived conditions — “pause when sentiment is negative and case is in Tier 1.” That’s powerful and a trap. AI-derived conditions can flicker. The case sentiment swings on each new email, and the SLA pause/resume cycles repeatedly. Each cycle leaves an entry in the KPI instance audit, and reports start showing strange “time paused” values.
If you adopt AI-derived pause conditions, add a hysteresis: require the condition to hold for 15 minutes before pausing, and require the resume condition to hold for 15 minutes before resuming. Implement it in a Power Automate guard before the SLA evaluation triggers. Saves the noise and keeps the math clean.
What to Do This Week
Open the SLA admin area for your top three SLAs by volume. For each, write the pause condition and the resume condition on a single line. Read them out loud. If the resume isn’t the exact inverse, that SLA has silently-paused KPIs in production. Pull the count and run the cleanup before next month’s compliance review.
