DEVOPS
Quarantine tests when Datadog flake rate crosses a threshold
Runs on a schedule, queries Datadog CI Test Visibility for tests whose flake rate exceeds a set threshold over the past week, quarantines them in GitHub.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionQuery Datadog CI Test Visibility for 7-day flake ratesDatadog
- LogicKeep tests above flake-rate threshold and run count
- ActionCommit quarantine annotation in GitHubGitHub
- ActionCreate ClickUp fix task per offenderClickUp
- OutputPost weekly quarantine digest to SlackSlack
What it does
It uses Datadog's CI Test Visibility data to find tests that have been statistically flaky over a rolling window, then isolates the worst offenders and creates a ClickUp task to fix each one.
When to use it
Use it when you already send test results to Datadog and want quarantine decisions driven by real flake-rate metrics over time rather than a single failing run. Good for teams that want a weekly cleanup pass instead of reacting to every red build.
How it works
- 1A weekly schedule starts the run.
- 2The flow queries Datadog CI Test Visibility for each test's flake rate over the trailing seven days.
- 3A logic step keeps only tests above the configured flake-rate threshold and minimum run count.
- 4For each qualifying test it commits a quarantine annotation to the repo via GitHub.
- 5It creates a ClickUp task in the engineering backlog with the metric, owning team, and a link to the Datadog test page.
- 6It posts a digest of everything quarantined this week to the channel.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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
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.