ENGINEERING
GitLab CI Severe Slowdown PagerDuty Escalation
Fires when a finished GitLab pipeline blows past a hard duration ceiling, confirms it is a sustained regression and not a one-off.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab pipeline finishedGitLab
- LogicCheck duration against hard ceiling; stop if under
- ActionFetch recent runs to confirm sustained regressionGitLab
- ActionBisect worst stage from job timingsGitLab
- OutputTrigger PagerDuty incident with stage detailPagerDuty
What it does
This is the urgent-path counterpart to trend watching. When a pipeline exceeds an absolute duration ceiling, it verifies the slowdown is sustained across the last few runs (so a single flaky run does not page anyone), identifies the worst stage, and opens a PagerDuty incident routed to the platform on-call.
When to use it
Use it when a slow CI directly blocks releases and a multi-minute regression is an operational emergency, not a backlog item. It guards the page with a confirmation check so on-call only wakes for real, repeating regressions.
How it works
- 1A GitLab pipeline webhook fires on completion.
- 2A logic step checks the total duration against the hard ceiling; runs under it stop.
- 3The flow fetches the last few runs to confirm the slowdown persists rather than being a single spike.
- 4It bisects the per-job timings to the stage carrying the largest share of the overage.
- 5A PagerDuty incident is triggered with the stage, duration, and pipeline link in the payload.
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 Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.