Skip to main content

One run, with every step in order

GET 
/api/flows/:flow/runs/:run

The trace: each node the runner touched, what it did, and how long it took. A Condition step carries both sides of the comparison and the verdict, which is what makes "why does my if/else only ever go one way" answerable at all.

Scoped to the flow rather than bound loose: a run id belonging to another flow (or, under RLS, another tenant) is a 404.

ONE CAVEAT, STATED RATHER THAN HIDDEN: flows.definition is edited in place, so a run inspected AFTER an edit shows steps whose config no longer matches what they ran with. A trace is truthful about what HAPPENED, not about what the flow said at the time; versioning is what closes that gap.

Request​

Responses​

The run and its steps.