DEVOPS
Edge Canary: Auto-Pause Cloudflare Worker Rollout on Error-Budget Burn
After a Cloudflare Worker deploy, watches the Honeycomb error rate against your SLO error budget and automatically halts the traffic shift the moment burn rate crosses threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerCloudflare Worker canary deploy webhookCloudflare
- ActionQuery Honeycomb for error-budget burn rateHoneycomb
- LogicBurn rate exceeds fast-burn threshold?
- ActionPin gradual deployment at current traffic splitCloudflare
- ActionOpen PagerDuty incident with version + burn detailPagerDuty
- OutputPost freeze decision and trace link to SlackSlack
What it does
Guards a progressive Cloudflare Worker rollout. When a new version is deployed and traffic begins shifting, this workflow polls Honeycomb for the live error budget burn rate. If burn exceeds your threshold during the canary window, it freezes the gradual deployment at its current percentage so the bad version never reaches 100% of traffic, then pages on-call.
When to use it
Run this whenever you ship edge code with Cloudflare's gradual deployments and you have an SLO defined in Honeycomb. It replaces the manual "watch the dashboard for ten minutes after deploy" ritual with an automated kill switch.
How it works
- 1A Cloudflare deployment webhook fires when a new Worker version starts receiving canary traffic.
- 2The workflow queries Honeycomb for the error-budget burn rate over the canary window.
- 3A logic branch compares burn rate to your threshold (e.g. 2x fast-burn).
- 4If healthy, it does nothing and lets the rollout continue. If burning, it calls the Cloudflare API to pin the gradual deployment at its current split.
- 5It opens a PagerDuty incident with the version, burn rate, and frozen percentage.
- 6It posts the freeze decision and a Honeycomb trace link to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.