PagerDuty Alerts for Cron Job Failures
Connect CronJobPro to PagerDuty and turn every cron job failure, timeout, or circuit-breaker trigger into an actionable PagerDuty incident — routed to the right on-call engineer automatically. Resolve incidents the moment your job recovers, keeping your alert history clean.
Start freeHow PagerDuty alerts work
When a CronJobPro job fails — whether due to a non-2xx HTTP response, a timeout, a connection or DNS error, or a missed heartbeat — CronJobPro fires a trigger event to your PagerDuty service using the Events API v2. If you have configured an alert threshold, notifications are suppressed until that number of consecutive failures is reached, preventing noise from transient blips. When the job subsequently succeeds, CronJobPro sends a resolve event to automatically close the open PagerDuty incident.
Set up PagerDuty notifications
You'll need your PagerDuty Events API v2 Integration Key (Routing Key).
- 1
Add an Events API v2 integration in PagerDuty
In PagerDuty, open the service you want to receive cron alerts. Go to Integrations → Add Integration, search for "Events API v2", and add it. PagerDuty will generate an Integration Key (also called a Routing Key) — copy it.
- 2
Open Notification Settings in CronJobPro
Log in to CronJobPro and navigate to Settings → Notifications. Click "Add Channel" and select PagerDuty from the channel type list.
- 3
Paste the Routing Key
Enter a name for this channel (e.g. "Production On-Call") and paste the PagerDuty Integration Key you copied into the Routing Key field. Save the channel.
- 4
Attach the channel to your jobs or monitors
Open any scheduled HTTP job or heartbeat monitor, go to its Notifications tab, and select the PagerDuty channel you just created. You can attach the same channel to multiple jobs.
- 5
Set an alert threshold (optional)
On each job you can configure an alert threshold — for example, 2 consecutive failures — so CronJobPro only pages on-call when the problem is persistent rather than a one-off transient error.
- 6
Test the integration
Trigger a test notification from the channel settings page to verify a PagerDuty incident is created and visible in your service. Confirm that a resolve event closes the incident as expected.
Frequently asked questions
What events cause CronJobPro to trigger a PagerDuty incident?
A PagerDuty incident is triggered when a job fails after your configured retries — this includes non-2xx HTTP responses, timeouts, and connection or DNS errors. Heartbeat monitors alert when the expected ping does not arrive within the grace period. A separate trigger fires when the circuit breaker auto-disables a job after repeated failures.
Will PagerDuty incidents be resolved automatically when a job recovers?
Yes. When a previously failing job completes successfully, CronJobPro sends a resolve event to PagerDuty using the same dedup key, automatically closing the open incident without any manual action.
Can I send alerts from multiple jobs to the same PagerDuty service?
Yes. Once you have saved a PagerDuty channel in Settings → Notifications, you can attach it to as many jobs and heartbeat monitors as you like. Each job generates its own incident with a unique dedup key so that incidents are tracked and resolved independently.
Does CronJobPro support heartbeat and dead-man's-switch monitoring in addition to scheduled jobs?
Yes. Beyond running scheduled HTTP cron jobs, CronJobPro also monitors heartbeat endpoints — services that are expected to call in on a regular schedule. If a ping does not arrive within the configured window, CronJobPro treats it as a failure and notifies your PagerDuty channel just like any other job failure.
Other integrations
Monitor your cron jobs in PagerDuty
Schedule HTTP jobs and heartbeat monitors, then get failure and recovery alerts where your team already works.