Read run history and traces
The runs list, per-run traces and logs, and the run pages hanging off a graph.
/runs is execution history across graphs, filterable by graph id and state. Open a run to replay its trace, read its logs, resume it if it suspended, or attach the editor to it if it is an active debug session.
- A graph's own history is under Graph info → Runs, alongside its revisions, authors, checks, and source.
- Run logs have verbosity levels — raise the level when a failure does not explain itself, rather than guessing from the summary.
- A run records the input and node arguments it used, which is what makes "use last run values" possible in Run cfg.
Related
- Read a run's pageRunning & debuggingWhat each panel of a run's page shows — summary, controls, path, logs, output, and the execution trace.
- 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.
- Live runs, suspension, and resumingRunning & debuggingWhere a currently-executing run shows up, why its history page can 404, and how suspended runs continue.
- Run configuration and presetsRunning & debuggingPer-node arguments for a run, saved as named presets you can duplicate, export, and seed from the last run.
More in Running & debugging · Search all help