How do I view my run history in Playbooks?

When something goes wrong in a Playbook, you need to know exactly where and why. Run History in Playbooks gives you a complete audit trail: execution details, step-by-step logs, and the distinction between draft and published versions that ran. This tutorial covers how to navigate and use Run History effectively.

Key takeaways

  1. Click the Run History button at the top of the Playbook editor to open the history panel showing all past executions.
  2. Each Run History entry shows the date, inputs used, and generated output.
  3. Click any entry in Run History to expand it and review the complete output from that run.
  4. All Playbook runs are saved permanently; you can access runs from days or weeks ago at any time.
  5. Copy inputs from a successful past run to quickly start a new run with the same or similar parameters.

Tutorial overview

Run History gives you a complete record of every Playbook execution. Each time a Playbook runs, AirOps logs the inputs, outputs, step-by-step status, and timing so you can review what happened and why.

You'll find Run History inside any Playbook. It shows the run name, whether it used a published version or a draft, and exactly when it ran. Click into any run to inspect the full execution path, including which steps succeeded, which failed, and how long each took.

Debugging depends on visibility. When a Playbook doesn't produce the expected output, Run History is where you diagnose the problem. You can trace the exact inputs that triggered an issue and see precisely where the process broke down. Run History also tracks both version-based and draft-based runs, so you can compare performance across different iterations of the same Playbook.

Practice

  1. How to View Run History in Playbooks

    Run History gives you a complete record of every Playbook execution. This tutorial shows how to access the Run History panel from the Playbook Builder and review past runs including their inputs, outputs, and status.