Hold a value and all downstream work until a person approves, or stop the owning flow without charging for the checkpoint itself.
Where: Flowgen → Add → Flow control → Pause for Approval
Key ideas
- Pass-through gate: The node does not transform the input. Approve passes it downstream unchanged; Stop cancels the owning run.
- Zero-cost checkpoint: The pause itself has no model cost, making it appropriate before expensive, external, or irreversible branches.
- Nested semantics: Inside a group or loop, approval pauses that owning execution scope; stopping prevents its remaining downstream work.
- Pause for Approval card: ApprovalNode uses the authored shared-card path. Gate downstream execution until a person approves, requests an AI revision, or stops the flow.
- Properties sidebar: Card/modal owned; common properties shell
- Opened surfaces: Output preview; group expansion
Steps
- Place the checkpoint immediately before the action that needs human review.
- Connect the value/artifact a reviewer must inspect and name the checkpoint by decision.
- Run the flow and review the upstream result, cost, destination, and route context when it pauses.
- Choose Approve to continue unchanged or Stop to cancel; fix upstream work and rerun rather than approving a known-bad result.
Pause for Approval controls and presets
- Add path: Flowgen → Add → Routing & Layout → Pause for Approval.
- Card: ApprovalNode.
- Properties: Card/modal owned; common properties shell.
- Controls: Label/note; status; gated targets; Approve; Ask AI to fix; Stop.
- Opened surfaces: Output preview; group expansion.
Tips
- Use one checkpoint per meaningful decision, not after every harmless transform.
- Put the gate before publish, send, write, delete, high-cost render, or a branch with external side effects.
Troubleshooting
The flow appears stuck
Look for a waiting Approval node in the active group/loop and choose Approve or Stop; downstream queued work will not start while it waits.