Execute the connected graph in dependency order while reading queued, running, done, error, and skipped states across groups, loops, routes, and approval pauses.
Where: Flowgen toolbar → Run flow
Key ideas
- Dependency scheduling: Runnable nodes start only after required upstream outputs are ready; independent branches may progress without waiting for unrelated work.
- Visible state: Canvas status chips and the run indicator distinguish queued, running, done, error, and skipped work so a stalled branch can be traced.
- Control-flow aware: Routes activate only the selected door, approvals pause downstream work, and nested groups/loops preserve their local run scope and cancellation.
Steps
- Test expensive or fragile nodes/groups individually with representative inputs.
- Confirm routes have a fallback, retries are bounded, and approval checkpoints sit before irreversible work.
- Choose Run flow and monitor status from upstream inputs through the final outputs.
- If a node fails, inspect its error and inputs, fix it, then rerun the narrowest safe scope before rerunning everything.
Tips
- Keep expensive final render/publish actions behind an approval while developing.
- Name major groups so run status identifies the stage, not only an internal node id.
Troubleshooting
A node remains skipped
Trace upstream status and route choice. Skipped usually means its branch was not selected or a required predecessor did not produce a usable output.