ENGINEERING
Flaky-vs-Real Triage via Sentry Correlation
When a GitLab test fails, checks whether Sentry recorded a matching production error in the same code path.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab pipeline failed webhookGitLab
- ActionQuery Sentry for matching prod errors in same pathSentry
- LogicBranch: correlated regression vs flaky-only
- ActionOpen PagerDuty incident for real regressionsPagerDuty
- OutputLabel uncorrelated failures flaky::review in GitLabGitLab
What it does
Distinguishes flaky failures from real regressions by cross-referencing each failing test against live Sentry issues touching the same file or module. A failure with a correlated production error is treated as a real bug and paged out; a failure with no production signal is labeled flaky for quarantine review.
When to use it
Use it when blanket-quarantining failing tests risks hiding real regressions. This adds a production-evidence check before anything gets silenced.
How it works
- 1A GitLab pipeline-failed webhook delivers the failed test list and changed files.
- 2For each failure, a Sentry query looks for unresolved issues whose stack frames touch the same source path within the recent release window.
- 3A logic branch splits failures into "correlated with prod error" versus "no production signal."
- 4Correlated failures trigger a PagerDuty incident with the Sentry issue and pipeline links attached.
- 5Uncorrelated failures get a GitLab `flaky::review` label and a comment noting no matching Sentry activity.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SentryErrors, performance, releases.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.