Skip to main content
Route Bolt run failures into the on-call stack your team already watches. When a schedule fails, an incident trigger creates an incident in PagerDuty, Datadog, incident.io, or New Relic, with a link back to the run. This guide adds one to a schedule.
PrerequisitesEstimated time: 10 minutes.

Steps

1

Add an incident trigger to the schedule

On the schedule, open the Triggers integration section, select Add integration, and choose your tool (for example, PagerDuty).
2

Configure the incident

Set the fields that shape the incident created on failure. For PagerDuty, for example: the from email, incident type, impacted service, urgency, priority, escalation policy, and any extra users to notify. Select Confirm to activate the trigger for this schedule.
Incident triggers only fire on failed runs. Successful runs never create an incident.
3

Or define it as code

If you manage schedules as code, configure the incident trigger in the schedule’s integrations block instead of the UI.
Trigger a failing run. Paradime creates an incident in your tool with the schedule name, workspace, run ID, and a link to the Paradime run logs. Each trigger runs independently, so if one tool errors, the others still fire.

Next steps

Set up alerts

Customize the Slack and Teams messages for the same failures.

Set up self-healing

Attempt an automatic fix before paging a human.

Trigger integrations reference

Every incident tool and its fields.

Incident templates

Template-based incident creation, including Rootly.