DEVOPS
Escalate long-overdue flags to their owner and on-call
Daily, finds feature flags more than 30 days past their kill-date, DMs the owning engineer in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionLoad expired flags and owners from GitHubGitHub
- LogicBucket flags into 30-day and 90-day tiers
- ActionDM owning engineer for 30-day flags in SlackSlack
- OutputOpen PagerDuty incident for 90-day flagsPagerDuty
What it does
Applies escalating pressure to flags that everyone keeps ignoring. It grades each stale flag by how far past its kill-date it is and routes accordingly: a gentle Slack nudge to the owner at 30+ days, and a tracked PagerDuty incident for the platform team at 90+ days so it can't be silently dropped.
When to use it
When filed tickets get ignored and flag debt becomes a reliability risk. Use it as the accountability layer on top of your scanning workflow so the worst offenders surface to on-call.
How it works
- 1A daily schedule starts the run.
- 2The flow loads expired flags with their kill-dates and owner from the flag annotations in GitHub.
- 3A logic step buckets each flag into 30-day or 90-day overdue tiers.
- 4For 30-day flags it sends the owning engineer a direct Slack reminder with the file links.
- 5For 90-day flags it opens a low-urgency PagerDuty incident assigned to the platform escalation policy.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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
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.