ENGINEERING
Open a Flake Issue When Datadog Flake Rate Crosses Threshold
Runs on a schedule, queries Datadog CI Visibility for each test's flake rate over the last 7 days.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery Datadog CI Visibility for 7-day flake rate by testDatadog
- LogicKeep tests above flake-rate threshold
- LogicDedupe against tests with an open issue
- ActionUpsert Linear issue with flake rate and dashboard linkLinear
- OutputPost newly flagged tests digest to SlackSlack
What it does
Instead of reacting to a single failure, this watches the trend. It pulls per-test flake rates from Datadog CI Visibility and escalates only tests that are statistically flaky over a rolling window — cutting noise from one-off failures while catching chronic offenders.
When to use it
Use it when you already ship test results to Datadog and want a data-driven quarantine policy rather than knee-jerk reactions to individual red builds.
How it works
- 1A scheduled trigger fires every morning.
- 2An action queries the Datadog CI Visibility API for flake rate by test over the last 7 days.
- 3A logic step filters to tests above your configured flake-rate threshold (e.g. >5%).
- 4A second logic step deduplicates against tests that already have an open issue.
- 5An action upserts a Linear issue per qualifying test, with the current flake rate, run count, and a Datadog dashboard link.
- 6A final output posts a digest of newly flagged tests to the team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect LinearIssues, projects, cycles, triage.
- 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 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.