Read a run's page
What each panel of a run's page shows — summary, controls, path, logs, output, and the execution trace.
Open a run from Runs, from a graph's Graph info → Runs, or from a notification. The top shows the run id, template, state, a Debug badge for debug runs, and the node and level it is currently on. Tiles give when it ran, how long it took, how many nodes executed, succeeded, and failed, and a link to the graph. A failed run shows its error first.
Panels, top to bottom
- Live debug
- Debug runs only: step and continue controls — see Debug with breakpoints.
- Run control
- Pause, stop, or resume the run — see Pause, stop, and resume a run.
- Debug from checkpoint
- For a paused or suspended normal run: open it in the editor as a debug session.
- Path through the graphs
- Each level the run entered, in order — see Follow a run's path.
- Run logs
- The execution log with levels, categories, and find — see Run logs and output.
- Output — stdout & stderr
- What the graph printed. Hidden when it printed nothing.
- Execution trace
- Every event, filterable by All / Nodes / LLM / Tools, live over SSE or replayed. Raw JSON shows the payloads.
Related
- Run logs and outputRunning & debuggingFilter a run's log by level and category, find text in it, and read what the graph printed to stdout and stderr.
- Follow a run's path through the graphsRunning & debuggingSee every level a run entered — sub-graphs included — and the nodes it executed in each.
- Pause, stop, and resume a runRunning & debuggingControl a live run from its page, resume a paused or suspended one, or reopen it in the debugger.
- Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
More in Running & debugging · Search all help