ENGINEERING
Stale Quarantine Escalation to PagerDuty
Scans open flaky-test quarantine issues on a schedule and escalates ones aging past an SLA to PagerDuty so quarantined tests don't rot indefinitely.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionQuery open flaky-test issues in LinearLinear
- LogicBucket issues by age vs SLA
- ActionNudge assignee on warning-stage issuesLinear
- ActionOpen PagerDuty incident for SLA breachesPagerDuty
- OutputPost quarantine backlog digest to SlackSlack
What it does
Quarantining a flaky test is meant to be temporary, but skipped tests have a way of staying skipped forever. This workflow audits open quarantine issues on a schedule and escalates any that have aged past your SLA — pinging the assignee and, if truly stale, paging the on-call lead via PagerDuty.
When to use it
Use it once you have a quarantine backlog and want a forcing function so coverage doesn't silently erode. It enforces a "fix or formally remove within N days" policy.
How it works
- 1A weekly schedule starts the audit.
- 2The flow queries Linear for all open issues labeled `flaky-test` with their creation dates.
- 3A logic step buckets issues by age against the SLA (e.g. warn at 14 days, escalate at 30).
- 4Warning-stage issues get a nudge comment to the assignee in Linear.
- 5SLA-breaching issues trigger a PagerDuty incident routed to the test-platform on-call.
- 6It posts a digest of the quarantine backlog and escalations to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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
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.