DEVOPS
Escalate flag rollouts that stall mid-ramp without reaching 100%
Detects flags parked at a partial rollout percentage past their planned completion time, and nudges the owner in Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts the stale-rollout sweep
- ActionList active flags and last-change timestamps via GitHubGitHub
- LogicBranch: rollout still partial past completion window?
- ActionNudge the flag owner in Slack to resolveSlack
- LogicBranch: unresolved since a prior run past grace period?
- OutputEscalate stale rollout to on-call via PagerDutyPagerDuty
What it does
Finds half-finished rollouts — flags left at 25% or 50% long after they should have hit 100% or been removed — and drives them to a decision before they become forgotten technical debt or silent risk.
When to use it
Use when flags tend to linger at partial exposure because the owner got pulled onto something else. It keeps your flag inventory clean and surfaces ramps that quietly stopped progressing.
How it works
- 1A daily schedule kicks off the sweep.
- 2A GitHub action lists active flags and the timestamp of their last percentage change.
- 3A logic branch flags any rollout still partial past its planned completion window.
- 4For each stale rollout, a Slack message nudges the named owner to finish, hold, or roll back.
- 5A logic step checks whether the same flag was already flagged on a previous run without resolution.
- 6If still unresolved past the grace period, a PagerDuty low-urgency alert escalates to on-call.
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
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.