DEVOPS
Vercel Budget Breach Rollback Triage via PagerDuty
When a production deploy breaches both the bundle-size and build-time budgets, pages the on-call engineer through PagerDuty and posts the candidate rollback target…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel production deploy succeeded webhookVercel
- ActionLoad baseline sizes and build-time historyPostgres
- LogicCheck for simultaneous bundle + build-time breach
- ActionTrigger PagerDuty incident for on-callPagerDuty
- OutputPost rollback candidate and diagnostics to SlackSlack
What it does
Handles the serious case where a production build blows past both the bundle-size and build-time budgets at once, signaling a likely bad ship. It pages on-call, identifies the last known-good deploy as a rollback candidate, and assembles the diagnostics needed to decide whether to revert.
When to use it
Use it as the escalation layer above your routine gates and digests, reserved for production deploys that breach multiple budgets simultaneously. Good for teams with a real on-call rotation who want a fast, structured path from regression to rollback decision.
How it works
- 1A Vercel production deployment-succeeded webhook delivers the new build's metrics.
- 2The flow loads the baseline sizes and recent build-time history from Postgres.
- 3A logic step checks whether both the bundle and build-time budgets are breached; single breaches exit quietly.
- 4On a double breach it triggers a PagerDuty incident for the platform on-call.
- 5It posts a Slack incident thread with the breaching routes, build duration, and the last passing deploy as the suggested rollback target.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.