DEVOPS
Overdue Feature-Flag Escalation to Owner and PagerDuty
Daily checks for flags more than 14 days past their sunset date, escalates each to its owner in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionRead registry and compute days overduePostgres
- LogicGrade flags by overdue severity
- ActionNudge owners of overdue flags in SlackSlack
- ActionPage on-call for severely overdue flagsPagerDuty
- OutputPost overdue leaderboard to SlackSlack
What it does
Applies real pressure to flags that have blown past their sunset date. Each day it grades overdue flags by how late they are, nudges owners directly, and escalates the worst offenders to on-call so chronic flag debt can't hide.
When to use it
Use it when removal PRs alone aren't getting merged and you need an accountability loop. Pairs well with a scanner that already opens the PRs.
How it works
- 1A daily schedule starts the run.
- 2The flag registry in Postgres is read and each flag's days-overdue is computed from its sunset date.
- 3A logic step splits flags into mildly overdue (14+ days) and severely overdue (30+ days).
- 4Owners of mildly overdue flags get a direct Slack nudge with the open removal PR link.
- 5Severely overdue flags trigger a PagerDuty incident routed to the platform on-call.
- 6A Slack roll-up posts the full overdue leaderboard to the engineering channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.