When it appears
- A static workflow graph includes a
human_wait(or equivalent approval) node. - An agent run interrupts and waits for a resume command (for example after a tool that requires confirmation).
Resume a paused workflow execution
AfterPOST /api/v1/workflow/manager/execute/{id} returns a thread ID, if the run pauses:
POST /api/v1/workflow/manager/executions/thread/{threadId}/resume
Send any required input in the body (see resume schemas in the API reference). Use this for static workflow runs that wait for user input or approval.
Resume in the Chat / Threads API
For Graphify-style agent runs, join or continue the stream and send a command such as{ "resume": { "decisions": [...] } } when the run is interrupted. See Threads and Chat run schemas in the API reference (command.resume on run input).
Product tips
- In the dashboard, open the execution detail to see where the run stopped.
- Disable triggers while you change approval steps if concurrent fires are a risk.
- Keep public widgets on workflows that do not expose unchecked high-impact tools without approval.
Related
- Workflows and agents
- Workflows
- Threads
- Native tools: Workflow —
human_waitnodes on static graphs