DEVOPS
Stuck-Pipeline Lead-Time Guard with PagerDuty Escalation
Hourly, scans GitLab for pipelines stuck or pending far beyond normal, and when a production deploy's lead time blows past the SLA it triggers a PagerDuty incident so on-call can…
How it runs
The automated pipeline, trigger to output.
- TriggerHourly schedule
- ActionFetch running and pending production pipelinesGitLab
- LogicCompute elapsed time and lead-time impact
- LogicKeep pipelines past the SLA threshold
- OutputTrigger PagerDuty incident per breachPagerDuty
What it does
This protects lead time at the source by catching deploys that are stalling in the pipeline. Instead of measuring after the fact, it detects in-flight production pipelines that have exceeded their expected duration and escalates them before they wreck the team's DORA numbers.
When to use it
Use it when slow or hung CI/CD is your dominant lead-time risk and you want on-call to intervene on a blocked production deploy rather than discovering it in a weekly report.
How it works
- 1An hourly schedule starts the scan.
- 2An action queries the GitLab API for running and pending pipelines targeting production environments.
- 3A compute step calculates each pipeline's elapsed time from creation and projects its lead-time impact.
- 4A logic branch keeps only pipelines that have exceeded the configured SLA duration.
- 5For each breaching pipeline, the output step triggers a PagerDuty incident with the project, pipeline link, elapsed time, and owning team, routing it to the platform on-call escalation policy.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.