DEVOPS
Edge Canary: Scheduled Promotion Gate for Cloudflare Gradual Deploys
On a fixed cadence during the canary bake, compares canary-version error rate against the stable baseline in Honeycomb and either advances the traffic percentage one step…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule tick during rollout window
- ActionRead current gradual-deployment split from CloudflareCloudflare
- ActionQuery Honeycomb canary vs stable error ratesHoneycomb
- LogicCanary within allowed delta of baseline?
- ActionAdvance traffic to next percentageCloudflare
- OutputPost rung decision to SlackSlack
What it does
Drives a Cloudflare gradual deployment forward step by step on a schedule instead of all at once. Every interval it pulls the canary version's error rate and the stable version's error rate from Honeycomb, compares them, and only bumps the traffic split if the canary is no worse than baseline. A regression holds the rollout where it is and alerts.
When to use it
Use when you want a hands-off, time-boxed promotion ladder (5% then 25% then 50% then 100%) for edge code, with each rung gated by real comparative telemetry rather than a fixed timer alone.
How it works
- 1A schedule fires every N minutes during an active rollout window.
- 2The workflow reads the current gradual-deployment split from the Cloudflare API.
- 3It queries Honeycomb twice — canary version errors and stable version errors — partitioned by version tag.
- 4A logic branch checks whether canary error rate stays within the allowed delta of baseline.
- 5If clean, it advances Cloudflare to the next configured percentage. If regressed, it leaves the split untouched.
- 6It posts the rung decision (advanced or held, with both error rates) 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 SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.