ENGINEERING
Alert-driven auto-rollback with PagerDuty escalation
Listens for a Sentry alert that a just-promoted release's crash-free rate has dropped below threshold, immediately re-aliases the previous Vercel deployment.
How it runs
The automated pipeline, trigger to output.
- TriggerSentry crash-free breach alert webhookSentry
- LogicAlert matches active production release?
- ActionLook up previous good deployment in PostgresPostgres
- ActionRe-alias Vercel production to previous buildVercel
- ActionOpen PagerDuty incident with detailsPagerDuty
- OutputAnnounce rollback in SlackSlack
What it does
Reacts to failure after promotion rather than gating before it. When Sentry fires a metric alert that the current production release's crash-free session rate has fallen below the line, the flow rolls production back to the last known-good Vercel deployment and pages the on-call engineer with context.
When to use it
Use it as a safety net behind a promotion gate, or on its own when releases go straight to production and you need fast, automatic reversion the moment real users start crashing. Ideal for teams with a PagerDuty on-call rotation that want rollback to happen before a human even acks.
How it works
- 1A Sentry metric alert webhook fires when the production release breaches the crash-free threshold.
- 2A branch confirms the alert is for the active production release and not a stale one.
- 3The flow looks up the previous known-good deployment ID stored in Postgres.
- 4It re-aliases the Vercel production domain to that previous deployment.
- 5It opens a PagerDuty incident with the release tag, crash-free rate, and rollback target.
- 6It posts the rollback action to Slack so the wider team sees it instantly.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect VercelDeploys, runtime logs, analytics.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.