DEVOPS
Confirm Flag Rollout in Datadog, Then Open GitHub Cleanup Issue
For each fully rolled-out flag, checks Datadog to confirm the off-variant code path has had zero evaluations for the threshold window.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule starts the run
- ActionList flags at 100% rolloutHTTP webhook
- ActionQuery Datadog for off-variant evaluationsDatadog
- LogicKeep only flags with zero off-variant hits
- ActionOpen GitHub cleanup issue per flagGitHub
- OutputAssign issue to code ownerGitHub
What it does
This sweep treats a flag as truly safe to remove only when telemetry agrees. For every flag at 100%, it queries Datadog for evaluations of the losing variant over the threshold window; if that path has fired zero times, it opens a GitHub issue to strip the flag.
When to use it
Use it when you've been burned by deleting a flag that still had a live code path. Pairing the flag state with real Datadog evaluation metrics means cleanup issues only land for flags that are genuinely inert.
How it works
- 1A daily schedule starts the run.
- 2An action lists flags currently serving one variant to 100% of traffic.
- 3For each, an action queries Datadog for off-variant evaluation counts over the window.
- 4A logic step keeps only flags with zero off-variant evaluations.
- 5An action opens a GitHub issue per qualifying flag, linking the flag key and the Datadog query.
- 6The output assigns the issue to the flag's code owner.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.