ENGINEERING
Flaky Test Rate Monitor with Datadog Threshold
Runs on a schedule, queries Datadog CI Visibility for each test's flaky rate over the last 7 days.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionQuery Datadog for per-test flaky ratesDatadog
- LogicKeep tests above the flaky-rate threshold
- ActionOpen or update ClickUp tech-debt itemClickUp
- LogicBranch on severe vs moderate flakiness
- OutputRaise PagerDuty incident for severe offendersPagerDuty
What it does
It measures how flaky each test actually is instead of reacting to single failures. On a daily schedule it asks Datadog CI Visibility for every test's flaky rate over a rolling window, and escalates only the tests that breach a configurable threshold so the worst offenders get attention first.
When to use it
Use it when single-failure alerts create noise and you want to prioritize quarantine work by real impact. It is ideal for teams already sending CI test results to Datadog.
How it works
- 1A daily schedule triggers the workflow.
- 2It queries Datadog CI Visibility for per-test flaky rate and failure count over the trailing 7 days.
- 3A logic step ranks tests and keeps any whose flaky rate exceeds the threshold (for example 5 percent).
- 4For each breaching test it opens or updates a ClickUp tech-debt item with the current rate.
- 5If the rate is severe it raises a PagerDuty incident routed to the owning service.
- 6It posts a ranked summary so the team sees the top flaky tests at a glance.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
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.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.