Flow Studio
Pause Workflow Node
Pausing a running workflow execution at its next safe checkpoint — the PauseWorkflowNode config and how to resume a paused execution.
Node Configuration
{
"nodeType": "PauseWorkflow",
"name": "pausePayrollRun",
"config": {
"executionId": "$output.startPayrollRun.executionId",
"reason": "Awaiting payroll data correction from HR system",
"resumeCondition": "manual"
}
}Configuration Fields
| Field | Type | Description |
|---|---|---|
executionId | string / expr | The running execution to pause. |
reason | string / expr | Reason for pausing, recorded in the execution audit log. |
resumeCondition | manual | timer | signal | manual: admin must explicitly resume. timer: auto-resume after resumeAfterMinutes. signal: resume when a specific signal is received. |
resumeAfterMinutes | int | Required when resumeCondition: "timer". Maximum: 10080 (7 days). |
Resuming a Paused Execution
POST /api/executions/{executionId}/resume
{
"action": "resume",
"reason": "HR data correction completed"
}Resuming can also be done by a workflow node using StartWorkflowNode targeting an orchestrator workflow that calls the resume API, or by a WaitForWorkflowNode that monitors a paused execution until it is manually resumed.
Pause vs. suspend: Pause (external control) is different from HIL suspension (internal node state). A paused execution can be resumed externally. An HIL-suspended execution resumes only when the HIL task is completed via the WorkDesk or API. Both show as
Suspended in the execution list.