Skip to main content

Runs

Runs are the first place to look when you need to understand what happened for one event.

Check:

  • flow id and version so you know which released graph shape actually executed
  • node progression so you can see which node_id, node_type, and service steps ran
  • status so you can separate ok, failed, and halted outcomes quickly
  • timestamps so you can tell whether the issue is missing execution, slow execution, or a downstream stall

The run record is intentionally practical: flow_run_id, flow_id, flow_version, optional trace_id, and a nodes[] array with per-node status, timing, service name, and error text. Run status is rolled up from node events: any failed node makes the run failed; otherwise a halted node makes it halted; otherwise it is ok.

The current endpoints are /api/v2/runs for cross-flow listings, /api/v2/flows/:id/runs for one flow, and /api/v2/flows/:id/runs/:flow_run_id for details. For hot flows, recent per-flow data may be served from the in-memory ring before Mongo.