SLA Not Triggering
Troubleshoot issues with SLA timers not starting or calculating correctly.
SLA Not Starting
Symptoms
- Request shows no SLA deadline
- SLA indicator shows "N/A"
- Timer not counting
Common Causes
-
No priority assigned
- SLA requires priority to determine tier
-
No SLA tier for priority
- Priority not mapped to any tier
-
Working hours not configured
- SLA can't calculate without working hours
-
Request status excludes SLA
- Some statuses may pause or not trigger SLA
Diagnosis Steps
-
Check request has priority
- Open request details
- Verify priority is set
-
Check SLA configuration
- Go to Settings > SLA Tiers
- Verify tier exists for priority
-
Check working hours
- Go to Settings > Working Hours
- Confirm hours are configured
-
Check priority mapping
- Go to Settings > Priority Mapping
- Verify priority maps to tier
SLA Showing Wrong Time
Symptoms
- Deadline seems incorrect
- Time remaining doesn't match expectation
- SLA breached unexpectedly
Common Causes
-
Timezone mismatch
- System and user timezone different
-
Working hours misconfigured
- Wrong start/end times
- Wrong days marked as working
-
Holiday not configured
- Public holiday counted as working day
-
Weekend settings wrong
- Tier includes/excludes weekends incorrectly
Diagnosis Steps
-
Verify timezone
- Check Settings > General > Timezone
- Compare with your local time
-
Review working hours
- Settings > Working Hours
- Verify correct times per day
-
Check holiday calendar
- Settings > Holidays
- Confirm holidays are entered
-
Review tier weekend settings
- Edit the SLA tier
- Check Saturday/Sunday inclusion
Example Calculation
If SLA seems wrong, manually calculate:
Request created: Friday 4 PM
Working hours: 9 AM - 6 PM
Resolution target: 8 hours
Weekend excluded for tier
Friday: 4 PM - 6 PM = 2 hours
Saturday: 0 hours (excluded)
Sunday: 0 hours (excluded)
Monday: 9 AM - 3 PM = 6 hours
Total: 8 hours
Due: Monday 3 PM
SLA Not Pausing
Symptoms
- Timer continues when should pause
- "Pending" status not stopping SLA
Common Causes
-
Pause not configured for status
- Status not set to pause SLA
-
Different pause rules
- Your expectation vs. configuration
Diagnosis Steps
-
Check pause configuration
- Settings > SLA Policies
- Review which statuses pause SLA
-
Verify status is correct
- Request actually in pause status?
SLA Notifications Not Sending
Symptoms
- No warning emails
- Missing breach alerts
Common Causes
-
Notifications disabled
- SLA alerts turned off
-
Email issues
- Spam filter
- Wrong email address
-
Threshold not reached
- Alert threshold not yet met
Diagnosis Steps
-
Check notification settings
- Settings > Notifications
- Verify SLA alerts enabled
-
Check email
- Spam/junk folder
- Correct email address
-
Review thresholds
- What percentage triggers warning?
- Has that threshold been reached?
Configuration Checklist
SLA Working Checklist
- Working hours configured
- Timezone set correctly
- SLA tiers created
- Priorities mapped to tiers
- Weekend settings correct
- Holidays entered
- Notifications enabled
Per-Request Checklist
- Request has priority
- Priority maps to tier
- Request status doesn't exclude SLA
- Request not manually paused
Quick Fixes
No SLA Showing
- Set or change priority
- SLA should recalculate
- Refresh the page
Wrong Calculation
- Review tier settings
- Check working hours
- Verify holidays
- Adjust if needed (affects new requests)
Notifications Missing
- Check spam folder
- Enable notifications
- Lower alert thresholds if needed
Escalation
If SLA issues persist after checking:
- Document the specific issue
- Note request ID and expected vs. actual
- Include configuration screenshots
- Contact DZDESK support
Related Topics
- SLA Management - SLA concepts
- SLA Policies - Configuration
- Working Hours - Time settings
- Weekend & Holiday Rules - Exclusions