ENGINEERING
Sweep Overdue Quarantine Re-Enable Deadlines and Escalate
Runs daily to find quarantined-test Linear issues past their re-enable due date, pings the owner.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionQuery Linear for overdue flaky-quarantine issuesLinear
- LogicBranch on first lapse vs repeat lapse
- ActionFirst lapse: ping assignee and bump due dateLinear
- ActionRepeat lapse: escalate to lead and open PagerDuty incidentPagerDuty
- OutputSend overdue digest to SlackSlack
What it does
Closes the accountability loop on quarantine. It finds tests that were parked but never fixed by their deadline and progressively escalates so quarantined tests don't become permanent dead coverage.
When to use it
Use this when your quarantine list keeps growing because tickets get filed but never resolved. It enforces the re-enable deadline instead of letting it quietly slip.
How it works
- 1A daily schedule kicks off the sweep.
- 2The workflow queries Linear for open issues labeled 'flaky-quarantine' with a due date in the past.
- 3A logic step branches on how overdue each issue is: first lapse versus repeat lapse.
- 4For a first lapse, it comments on the issue tagging the assignee and bumps the due date by 7 days.
- 5For a repeat lapse, it reassigns to the team lead, raises priority, and opens a low-urgency PagerDuty incident referencing the stale test.
- 6A digest of all overdue and escalated quarantines is sent to the engineering Slack channel.
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
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.