DEVOPS
Triage flaky release blockers and page the owning team
Triggered when a release-blocking pipeline fails, an agent decides whether the failure is a known flaky test or a real regression, quarantines confirmed flakes.
How it runs
The automated pipeline, trigger to output.
- TriggerRelease pipeline fails
- ActionAgent classifies each failure: flaky vs regression
- LogicRoute flakes and regressions to separate paths
- ActionQuarantine flakes and open GitHub tracking issueGitHub
- ActionTrigger PagerDuty incident for real regressionsPagerDuty
- OutputPost triage decision to SlackSlack
What it does
When a release pipeline goes red, this workflow distinguishes a flaky test from a genuine regression. Confirmed flakes get quarantined so the release can proceed; real failures page the owning on-call so a human investigates.
When to use it
Use it on release branches where a red pipeline is expensive and you need fast, defensible triage. It avoids paging humans for known-flaky noise while making sure actual regressions still wake someone up.
How it works
- 1A failed release pipeline fires the trigger with the failing test list and logs.
- 2An agent reviews each failure against historical flake data and the diff to classify it as flaky or a real regression.
- 3A logic step routes flakes and regressions down separate paths.
- 4For flakes, the agent commits a quarantine entry in GitHub and opens a tracking issue.
- 5For real failures, it triggers a PagerDuty incident assigned to the owning team.
- 6It posts the triage decision and reasoning to the release channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.