Guide
Configure Auto-Attach and Conditions
Decide when a runbook should appear automatically and what conditions should control each step.
Before you start
- Be clear whether the runbook should always be manual, always attach, or attach only for a narrow incident pattern.
Do this
- Open the runbook and choose the trigger mode:
Manual onlyif responders should decide when to launch it.Auto attach (always)if it should appear on every matching incident.Auto attach (conditional)if it should appear only when the incident matches rules.
- If you choose conditional attach, add the incident rules that matter most such as severity, status, phase, environment, labels, or incident age.
- Keep the condition set tight enough that the runbook only appears when it is genuinely useful.
- Add step-level conditions when a step should wait for a previous step, a phase change, a milestone, or a timer.
- Use wait and repeat settings only for steps that really need polling or delayed execution.
- Save the runbook and test it against one incident that should match and one that should not.
Check it worked
- The runbook appears on matching incidents and stays out of the way on non-matching ones.
- Wait or conditional steps do not fire too early.
- Responders can tell why the runbook is attached.
If it does not work
- If the runbook appears too often, remove broad conditions before you add more.
- If a step never runs, check its phase, milestone, previous-step, or delay rule.
- If the runbook should be optional, switch it back to
Manual only.
