DEVOPS
Auto-rollback a feature flag when Honeycomb error rate spikes
Polls Honeycomb for the error rate on a newly rolled-out flag cohort and, if it breaches your threshold versus the control group, disables the flag via GitHub and pages…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires every 2 minutes during rollout window
- ActionQuery Honeycomb for flag-on vs control error rateHoneycomb
- LogicBranch: flag-on error rate exceeds control by delta?
- ActionDisable flag config via GitHub commit / revert PRGitHub
- ActionRaise high-urgency PagerDuty incidentPagerDuty
- OutputPost rollback summary to Slack release channelSlack
What it does
Watches the live error rate for traffic exposed to a feature flag and pulls the flag automatically the moment it regresses against the control cohort, then escalates so a human knows within seconds.
When to use it
Run this during a progressive rollout (1% to 100%) of a risky backend change behind a flag. It gives you a deterministic safety net so a bad deploy never burns more than one polling interval of elevated errors.
How it works
- 1A schedule fires every two minutes during the rollout window.
- 2A Honeycomb query returns the error rate for the flag-on cohort and the flag-off control cohort over the last interval.
- 3A logic branch compares the two: if flag-on error rate exceeds control by more than the configured delta, proceed; otherwise stop.
- 4On breach, a GitHub action commits the flag config back to the disabled state (or opens a revert PR) to kill the rollout.
- 5PagerDuty raises a high-urgency incident with the offending flag, cohort sizes, and the Honeycomb query link.
- 6A Slack message posts the rollback summary to the release channel.
Set it up
What you configure once, before turning it on.
- 1Connect HoneycombDistributed traces and queries.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.