Run a Runbook During an Incident

Before you start

• Open the incident you are working.
• Check that the incident scope is accurate so OpsBell can prioritize the best matching runbooks.

Do this

1. In the incident command center, open Runbook Orchestration.
2. Review the recommended runbooks first because OpsBell sorts active runbooks by incident scope match.
3. Choose the runbook you want to launch.
4. Confirm the runbook is marked runnable and not blocked by an unready step.
5. Start the runbook and watch the execution record from the incident page.
6. Use the execution history to see which steps completed, failed, or waited.
7. If the runbook exposed gaps or dead steps, fix the definition after the incident instead of improvising inside the runbook editor mid-response.

Check it worked

• The runbook starts from the incident.
• The execution is visible from the incident record.
• Responders can see which steps ran and which still need attention.

If it does not work

• If no runbook is available, activate one in the runbook library first.
• If the selected runbook is blocked, fix the specific step readiness issue rather than rerunning it blindly.
• If the wrong runbook is recommended, adjust runbook targets so they match the incident scope better.

Next

• Use the command center
• Review runbook step types