Loading…
How do I read runs and run history?
TL;DR: Every playbook execution creates a run with step status, logs, and outputs. View past runs in the playbook's History tab. Click a run to inspect details — which steps succeeded, what data was produced, and any errors. Paused runs stay on the same History row until you Continue or Stop.
Who this is for
Builders and Members reviewing playbook execution results.
Where is run history?
Open a playbook and go to the History tab. You'll see a list of past runs with:
- Run status (success, failure, in progress, Paused /
suspended) - Start time and duration
- Trigger type (manual, schedule, webhook)
How do I inspect a run?
Click a run to open the detailed view:
- Graph — visual step progress for that run
- Logs — per-step stdout and error messages
- Outputs — data each step produced
What does Paused mean?
A Paused run has status suspended. Ballet freed the sandbox and is waiting for you (or an external notifier) to continue on the same runId. History keeps one continuous row — the badge flips Running → Pausing → Paused → Running.
While paused, run detail exposes state.resume (including requestId, prompt, details, and reason) and often an API resume (curl) snippet. Operator pause parks between steps; waitForInput parks mid-step for approval. See How do I pause and resume a playbook run?.
Can I compare runs?
Review consecutive runs in History to spot regressions — for example, a step that succeeded yesterday but fails today after a code change.
How do I share run results?
Use share run output to generate a link others can view without full Studio access.