ENGINEERING
Correlate flaky-test failures with Honeycomb traces before filing
When a quarantine candidate is detected, pulls the matching CI test-run traces from Honeycomb to find shared timeouts, slow spans, or resource contention.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: quarantine candidate detectedHTTP webhook
- ActionQuery Honeycomb traces for failing runsHoneycomb
- LogicIsolate recurring slow or erroring span
- OutputFile enriched Linear issue with root-cause signalLinear
What it does
Goes beyond "this test is flaky" to "here is why." For each quarantine candidate it inspects the distributed traces emitted by the test run, surfaces the common slow or erroring spans across failures, and attaches that evidence to the bug so an engineer starts with a hypothesis instead of a blank page.
When to use it
Use this when your test suite emits OpenTelemetry traces to Honeycomb and flakiness is suspected to come from timeouts, external calls, or contention rather than bad assertions. It makes triage dramatically faster.
How it works
- 1A webhook fires when the classifier marks a spec as a quarantine candidate, passing the spec name and recent failing run IDs.
- 2The flow queries Honeycomb for the traces tied to those run IDs, filtered to the failing test's spans.
- 3A logic step compares spans across the failing runs to isolate the recurring slow or error-status span.
- 4It composes a root-cause summary from the shared signal.
- 5A Linear issue is created with the spec, flake rate, the suspect span, and a Honeycomb query link, routed to the owning team.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect HoneycombDistributed traces and queries.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.