DEVOPS
Edge Canary: PagerDuty-Triggered Instant Worker Rollback
When a PagerDuty incident fires during an active canary, instantly rolls Cloudflare traffic back to the last known-good Worker version.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident triggered webhookPagerDuty
- LogicIs a canary deployment active?
- ActionRoll Cloudflare traffic back to stable versionCloudflare
- ActionVerify burn rate dropped in HoneycombHoneycomb
- LogicRecovered or still burning?
- OutputUpdate PagerDuty incident and notify SlackPagerDuty
What it does
Turns a PagerDuty page into an automatic edge rollback. If an incident is triggered while a canary deployment is live, this workflow immediately shifts Cloudflare traffic back to 100% on the previously stable Worker version, then verifies in Honeycomb that the error budget burn actually stops before declaring recovery on the incident.
When to use it
Use for high-blast-radius edge services where the right reaction to any page during a canary is "revert first, investigate later." It compresses the revert-and-confirm loop into seconds without a human at the keyboard.
How it works
- 1A PagerDuty webhook fires on a triggered incident tagged to the edge service.
- 2A logic branch confirms a canary deployment is currently active (otherwise it exits).
- 3The workflow calls Cloudflare to roll the gradual deployment back to 100% stable version.
- 4It waits, then queries Honeycomb to confirm the burn rate has dropped post-rollback.
- 5A second logic branch decides recovered versus still-burning.
- 6It posts a status note back to the PagerDuty incident and mirrors the outcome to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect HoneycombDistributed traces and queries.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.