DEVOPS
Scheduled Worker canary promotion after a clean bake period
On a timer, checks the current Cloudflare Worker canary against Axiom logs and automatically promotes it to full traffic once it has stayed below the error threshold…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every 15 min during bake
- ActionRead canary state from PostgresPostgres
- ActionQuery Axiom for canary error rateAxiom
- LogicUpdate clean-streak count vs. threshold
- ActionPromote canary to 100% when streak metCloudflare
- OutputRecord decision in Postgres and DiscordPostgres
What it does
Watches a Worker that is already serving partial canary traffic and decides, on a schedule, whether it has earned full rollout. Each run pulls the canary's recent error and latency metrics from Axiom; once the version has been clean across enough consecutive checks, the flow promotes it to 100% and stops watching.
When to use it
Use it for low-urgency rollouts where you want a long, hands-off soak rather than an immediate staged push. It is ideal for off-hours promotions where nobody is watching but you still want a clean-bake guarantee before going to full traffic.
How it works
- 1A schedule fires every 15 minutes during the bake window.
- 2The flow reads canary state (current %, version ID, consecutive-clean count) from Postgres.
- 3Axiom is queried for the canary version's error rate since the last check.
- 4A logic step increments the clean count if under threshold, or resets it to zero on a breach.
- 5When the clean count crosses the promote target, Cloudflare sets the split to 100% canary.
- 6State is written back to Postgres and a Discord note records the decision.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect DiscordCommunity channels + voice + bots.
- 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.