DEVOPS
Escalate Long-Overdue Flags: Page the Owner When Cleanup Stalls
Daily check for flags more than 90 days past kill-date with an open removal ticket that nobody has touched, then escalates via PagerDuty to the owning service's on-call.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule runs escalation check
- ActionQuery registry for flags 90+ days overduePostgres
- ActionCheck Linear ticket status and last activityLinear
- LogicKeep flags with stalled open tickets
- OutputOpen PagerDuty incident for owning servicePagerDuty
What it does
Finds feature flags that are severely overdue, more than 90 days past their kill-date, that already have an open Linear removal ticket which has seen no activity. For these stalled, high-risk flags it raises a PagerDuty incident against the owning service so the on-call engineer is accountable for closing it out.
When to use it
Use this as the last-resort tier of flag governance. Most cleanup should resolve via MRs and nudges; this catches the dangerous long-tail of forgotten flags wrapping production behavior that no reminder has shifted. Tune the threshold to your risk tolerance.
How it works
- 1A daily schedule runs the escalation check.
- 2It queries the Postgres registry for flags over 90 days past kill-date.
- 3It checks Linear for each flag's removal ticket and its last-activity timestamp.
- 4A logic step keeps only flags whose ticket is open and stale beyond the inactivity window.
- 5For each, it opens a PagerDuty incident routed to the owning service's escalation policy with flag context and the ticket link.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect LinearIssues, projects, cycles, triage.
- 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 DevOps workflows
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.