DEVOPS
Detect retry-pass flakes from CI and file a Linear quarantine ticket
Watches CI run-completed webhooks for tests that failed then passed on retry within the same run, and opens a deduplicated Linear issue tagging the test as a flake candidate.
How it runs
The automated pipeline, trigger to output.
- TriggerCI run-completed webhook receivedHTTP webhook
- LogicKeep only tests that failed then passed on retry
- ActionSearch Linear for existing flake issue by fingerprintLinear
- LogicBranch: skip if duplicate, otherwise file new
- ActionCreate labeled Linear quarantine issueLinear
- OutputReturn new Linear issue key
What it does
When your CI provider posts a run-completed webhook, this workflow inspects the per-test results and isolates any test that failed on its first attempt but passed on an automatic retry inside the same run. That signature is the clearest fingerprint of intermittent flakiness. For each one it opens a tracked Linear issue so the test stops getting silently swept under retries.
When to use it
Use it when your test runner retries failures automatically and the green checkmark hides real instability. It turns invisible retry-passes into a visible, owned backlog.
How it works
- 1CI sends a run-completed webhook with the full test result payload.
- 2A filter keeps only tests with attempt 1 = failed and a later attempt = passed.
- 3The workflow builds a stable fingerprint from the suite, file, and test name.
- 4It searches Linear for an existing open issue with that fingerprint to avoid duplicates.
- 5If none exists, it creates a Linear issue labeled flaky-quarantine with the failing assertion, retry count, and a link to the CI run.
- 6The new issue key is posted back as the workflow output.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.