Runs & debugging
Reading execution history, per-step results, and cancelling stuck runs.
Every firing of a workflow is a run (execution). The runs page per workflow shows them newest-first with status, timing, and what triggered them.
Runs newest-first: filter chips by status, and failed runs surface their error inline.
Run statuses
| Status | Meaning |
|---|---|
pending |
queued, not started |
running |
executing now |
waiting |
paused on a halting step (approval, wait, sub-workflow) |
completed |
finished cleanly |
failed |
a step errored — the run detail shows which one and why |
cancelled |
you stopped it |
Per-step results
Open a run to see every step's input, output, error, and timing — loop steps show one row per iteration. This is the fastest way to answer "why did my Slack message come out empty": find the step where the data went wrong and check what it actually received.
Asking Max
The canvas chat can read recent runs, so "why did the last run fail?" works — Max pulls the failing step's input/output and explains, or fixes the config and re-verifies.
Cancelling
A running or waiting run can be cancelled from the runs page — the
row flips to cancelled and the underlying job is killed immediately.
The workflows index
The health strip on Workflows is the at-a-glance version: runs and failures over the last 7 days, plus needs attention — the count of workflows whose latest run failed.