Live runs, suspension, and resuming
Where a currently-executing run shows up, why its history page can 404, and how suspended runs continue.
While a graph is executing, the editor's execution rail is the place to watch it — it polls the agent's active-runs endpoint. Debug sessions can also be attached to from the runs list.
A run that suspends is checkpointed by the agent: its heap and stack are persisted so it can be resumed later from the run page. Node configuration is not part of the checkpoint — a resumed run reads config from the graph and the arguments it was started with.
Related
- 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 a run's pageRunning & debuggingWhat each panel of a run's page shows — summary, controls, path, logs, output, and the execution trace.
- Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
- Debug with breakpointsRunning & debuggingPause execution at a node, step, inspect agent memory, and manage breakpoints across graphs.
More in Running & debugging · Search all help