Flow Studio
Processes Capability Overview
Managing workflow lifecycle from within a workflow — starting, cancelling, pausing, and querying other workflow executions to implement orchestration and saga patterns.
Orchestration vs. Sub-Workflows
| Pattern | Use When | Relationship |
|---|---|---|
| Sub-Workflow (Guide34) | Reusable child workflow, tight coupling, share actor context | Parent waits for child (sync) or fire-and-forget (async) |
| Processes Capability | Orchestrating independent workflows, saga compensation, cross-workflow coordination | Coordinator controls lifecycle of independent executions by ID |
Available Process Nodes
| Node Type | Operation | Output |
|---|---|---|
StartWorkflowNode | Start a new workflow execution | { executionId, status: "started" } |
CancelWorkflowNode | Send cancellation signal to a running execution | { executionId, status: "cancellation-requested" } |
PauseWorkflowNode | Pause a running execution at its next safe point | { executionId, status: "pausing" } |
ExecutionStatusNode | Query current status and output snapshot | { executionId, status, completedAt, output } |
WaitForWorkflowNode | Suspend until another execution completes | Target execution's output |
Orchestrator pattern: Use a dedicated "orchestrator" workflow that starts multiple child workflows, waits for their completion using
WaitForWorkflowNode, and coordinates the overall business process. This is the preferred pattern for distributed business transactions.