DEVOPS
Auto-purge then rollback when a deploy cratered the cache-hit ratio
After a Vercel production deploy, if the Cloudflare cache-hit ratio collapses, attempts a targeted cache purge first and re-measures; if it still fails, rolls back the deployment…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeededVercel
- ActionSample cache-hit ratio after bakeCloudflare
- LogicExit if healthy, continue if collapsed
- ActionTargeted Cloudflare purge, then re-sampleCloudflare
- LogicStop if recovered, else proceed to rollback
- ActionRoll back Vercel deploymentVercel
- OutputFile Linear issue with remediation trailLinear
What it does
This workflow is a self-healing guard for cache regressions. When a production deploy tanks the Cloudflare cache-hit ratio, it first tries the cheap fix, a targeted purge to clear stale or poisoned entries, then re-measures. If the ratio recovers, it stops. If not, it treats the deploy as the cause, rolls back to the previous production deployment, and files a tracked issue.
When to use it
Use it when origin load from a cache miss storm is expensive enough to justify automated remediation. It suits mature teams comfortable with automated rollback who want the system to attempt recovery and escalate to a human only when remediation fails.
How it works
- 1A Vercel production deployment-succeeded webhook fires.
- 2Sample the Cloudflare cache-hit ratio after a short bake window.
- 3Branch: if the ratio is healthy, exit; if it collapsed, continue.
- 4Issue a targeted Cloudflare cache purge and wait, then re-sample the ratio.
- 5Branch: if recovered, stop; if still failing, roll back the Vercel deployment to the prior production build.
- 6File a Linear issue capturing the deploy, the purge attempt, and the rollback for follow-up.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.