Rundeck performing auto-remediation of Incidents

I’ve just watched a webinar and understand that the 2 products can be configured so that a Rundeck job can automatically fix an issue without waking up a human responder - can you advise how this is achieved please, as it wasn’t demonstrated.


Hi Chris,

We have documentation and videos that walk through this at

You can also schedule a call with the Rundeck team on that page if you’re looking for an in-depth conversation on how you can best use Rundeck with PagerDuty.

Additionally, you can reach out to us at to explain your use-case and how you’d like to set up this workflow, and we’d be happy to connect you with the Rundeck team.


Cassie Champagne
Technical Support Specialist
PagerDuty Support

Hi Cassie,

Thanks for your response. I’ve finally reviewed the documentation and videos in the link you supplied but I couldn’t find anything that answered my query - it just states that Rundeck jubs can “Automatically trigger at the start of an Incident” …which is too late for my use case by then, as the first Responder will already have been called out and we want to avoid that happening. So I will go ahead and contact PagerDuty Support.


The recommendation I’ve seen from PagerDuty Solutions experts is to make the Rundeck Automation your first level contact. That stage triggers the automation and if the issue is fixed the incident can be closed. If the issue does not get resolved the Incident can be escalated to the next team which will send notifications to folks that can put hands on keyboards.

1 Like

Thanks for the update Forrest. Is there a link to documentation detailing how this could be set up please?

My best guess would be to configure the Rundeck job as a Service extension and then set a “dummy” user as the first level contact in the Escalation Policy, with a suitable time delay before escalating to the second level.

Apologies for the question, but a don’t have an environment readily available to test this in.