How to Fix PagerDuty Oncall Schedule
In this tutorial, you'll learn about How to Fix PagerDuty Oncall Schedule. We cover key concepts, practical examples, and best practices.
The Problem
Your PagerDuty oncall schedule configuration is not working. Notifications do not fire, incidents are not created, or the feature behaves incorrectly.
PagerDuty is critical for incident response, but oncall schedule misconfiguration leads to missed alerts and delayed responses. At DodaTech, we use PagerDuty for on-call management across all production services. Here is how we fix oncall schedule issues.
Error Symptoms
You see in the PagerDuty console:
Integration test failed
c53cabda6421 oncall-schedule configuration error
No incidents created
Wrong Configuration
This is the problematic oncall schedule setup:
{
"service": {
"name": "My Service",
"description": "Production service"
}
// Missing: oncall schedule configuration
}
Without proper oncall schedule fields, PagerDuty creates the service but does not apply the required routing, escalation, or notification rules.
API response:
HTTP 201 Created
Warning: oncall-schedule not configured - using defaults
Service created without oncall-schedule rules
Right Configuration
Here is the correct oncall schedule setup:
{
"service": {
"name": "My Service - pagerduty-oncall",
"description": "Production service managed by DodaTech SRE team",
"escalation_policy": {
"id": "ES12345"
},
"incident_urgency_rule": {
"type": "use_support_hours",
"during_support_hours": {
"type": "constant",
"urgency": "high"
},
"outside_support_hours": {
"type": "constant",
"urgency": "low"
}
},
"alert_creation": "create_alerts_and_incidents"
}
}
Expected output:
HTTP 201 Created
Service created successfully
Integration key: PD-c53cabda6421
Prevention
- Test service integrations with the PagerDuty API sandbox environment before production
- Configure escalation policies with proper timeout values and multiple notification levels
- Schedule maintenance windows for planned changes to prevent false alerts
- Use event orchestration for complex alert routing, deduplication, and suppression
- Set up runbook actions for automated incident response and resolution
- Review SLO targets to align alert severity with business impact
- Regularly audit on-call schedules for coverage gaps, especially during holidays
Common Mistakes with oncall schedule
- Using
headandtailinstead of pattern matching, causing runtime errors on empty lists - Forgetting that lazy evaluation defers computation until the value is forced, causing space leaks with unevaluated thunks
- Using
returnto exit a function early instead of wrapping a pure value in the monad
These mistakes appear frequently in real-world PAGERDUTY code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.
Practice Exercise
Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.
This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.
FAQ
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro