How‑to: Debug Workflow Runs

Find and fix issues using the run view in the workflow editor.

Open a run

Open your workflow and switch the sidebar to the Runs tab to see recent runs.
Filter the list by status (Running, Completed, Failed, Cancelled, Pending), pick a date range, or toggle Show debug runs.
Click a run to open it in the Live tab. The clock button jumps to the latest run; keep Auto-follow on to track new runs as they start.
Use the copy-link button in the run header to share a permalink to that exact run.

The Workflows list also shows each workflow’s last run status, and its Activity sidebar carries the same run list and run view.

The run header shows status, duration, who started the run, and which trigger fired. A chip marks what the run executed: Draft, Branch, Saved, a named release, or an editor Test run.
Expand Inputs and Results to see the data the run started with and what it produced.
Steps appear in execution order; steps that ran concurrently are grouped as parallel. Failed and running steps expand automatically, and the last step opens because it carries the run’s result.
Expand a step to view its inputs, outputs, timing, and errors. API Request steps show the response status, body, and collapsed headers.
While a run executes, nodes on the canvas highlight with their step status, and node ports show last-run values.
A run can finish with partial errors: the run header lists which nodes failed even though the run completed.

A Human Input step suspends the run and shows a response panel in the run view — approve or reject, type a text answer, or pick from options. Answering resumes the run.
A Wait step parks the run and resumes it automatically at the scheduled time; the run view shows when.
A Stop step ends the run early as a success; the run view notes that downstream nodes were not scheduled.

Adjust node settings and click Run (Cmd/Ctrl + Enter) to verify fixes. Editor runs are debug runs by default.
Use Retry Run in the run actions menu on a failed or cancelled run; the new run links back to the original.
Use Cancel Run to stop a running or suspended run.
Use Restore Draft to load the flow a run executed back into your draft — useful when the current draft has moved on since the failure.

Use a Manual Start trigger for rapid iteration.
Add Note nodes to document assumptions and expected shapes.
Streaming steps (shell commands, coding agents, AI) show their output live in the step card while they execute.

API 401/403: re-authorize the Connection in Connections and verify credentials and permissions.
Parse errors: inspect the response body in the step’s details; ensure the payload is valid JSON.
Run stuck in running: an external call may be hanging — check the step marked Live, or stop the run with Cancel Run.