Skip to content

Running Saved Flows

Pioneer provides two related paths:

  • Canvas → Run submits the current Canvas build, including unsaved edits.
  • Chat's saved-Flow run tool submits one guarded Saved Flow revision after explicit approval.

Use the saved-Flow path when stable identity and immutable saved-source provenance matter.

Run a Saved Flow with Chat

  1. Save or update the Flow in Canvas.
  2. Ask Chat to inspect the named Saved Flow. Include the Saved Flow ID when names could be ambiguous.
  3. Review the reported revision and executable fingerprint.
  4. Explicitly ask Chat to run that Saved Flow.
  5. Review the approval request and approve or deny that one execution.
  6. If the Flow contains a Script, review the separate nested Script approval when it appears.
  7. Open Executions and inspect the new run by its run ID.

Pioneer rechecks the revision and fingerprint after approval. A mismatch stops the submission as stale. It does not run whichever version happens to be current.

One approval, one consequence

Apply approval does not authorize a run. Run approval does not authorize a nested Script. An approval permits an attempt; execution and success remain separate evidence.

Provenance to expect

A guarded saved run records Saved Flow ID, revision, executable fingerprint, run ID, session ID, and submission time. Use that provenance—not the current Canvas or display title—to answer what ran.