Read precise run states, stop the intended execution scope, configure first-match routing, approve or stop a paused flow, and navigate open or resolved comments.
Where: Run a node, branch, group, list, batch, or flow; select a Route, approval checkpoint, or Comments.
Key ideas
- The runner follows dependencies: Ready independent branches can run in parallel; groups, lists, batches, and whole-flow runs keep a scope that can be cancelled independently.
- Routes are ordered: Cases are checked top to bottom and the first match wins. A broader earlier rule can make a later case unreachable.
- Approval pauses retain context: The checkpoint previews the latest output and waits for Approve, Ask AI, or Stop.
Steps
- Start the smallest intended scope: node, selection, group, list/batch iteration, or complete flow.
- Read card status: Waiting to run, Running, Waiting for your approval, Done, This step didn’t finish, or Skipped — a different path ran.
- Use Activity to reveal a running or failed node and read duration/error details.
- Cancel the owning scoped run when only one group/list/batch should stop; use the global stop only when every active run should stop.
- In Route, order cases from specific to broad and resolve any unreachable-case warning.
- Leave override at Auto — conditions decide, or choose the exposed controller that should force a route.
- At an approval checkpoint, open the latest-output preview, Approve to continue, Ask AI to review and fix the full connected flow, or Stop.
- Open Comments, toggle Pins are showing/hidden, select a row to go to its canvas pin, and use the Resolved section for closed threads.
- Retry a failure after correcting its cause; route retries respect their configured limit before falling through.
Status timing and routing
- Done and skipped states linger briefly before fading; errors persist until the next run.
- A route may report a note such as “ran 3× · limit reached”.
- A branch passes its main input unless a wired return supplies another value.
- Selecting a hidden comment turns pins back on so the target can be shown.
Tips
- Put catch-all route cases last.
- Use Ask AI at a checkpoint when the connected flow—not only the preview—needs diagnosis.
Limitations and important notes
- A skipped branch is not a failure.
- Stopping one scoped run does not necessarily stop unrelated parallel work.
Troubleshooting
A route case never runs.
Check for a broader case above it and confirm Auto or the controlling override is set as intended.
A comment pin seems missing.
Open Comments and select its row; Flowgen restores pin visibility and navigates to it.