Skip to content

Executions

An execution is one attempt to run a Flow snapshot. Executions answers “what actually ran?”; Canvas answers “what is configured now?”

Lifecycle

  • Running is live, non-terminal evidence.
  • Completed means the engine recorded terminal completion.
  • Failed means a block or job recorded failure.
  • Cancelled and timed out are shown only where the underlying operation recorded those states. A Script timeout, for example, normally anchors a failed Flow with timeout metadata.

Pioneer does not promise to resume an interrupted run or a pending approval after restart. Cancellation is not a claim that external effects were undone.

What to inspect

Select a run and read in this order:

  1. outcome and failure anchor;
  2. run and session IDs;
  3. source provenance, when recorded;
  4. stage order, duration, and row transitions;
  5. bounded terminal output and truncation state;
  6. approval request and decision evidence; and
  7. raw events only when more detail is needed.

Terminal output is the final stage's output, not every intermediate row. A successful status is not a correctness guarantee.

For an evidence-grounded investigation, copy the run ID and follow Diagnose, Repair, and Verify.