taskflow

Detached background jobs resume after a restart by using a durable flow identity to link child tasks and persisting orchestration state in stateJson. This single flow identity preserves the owner context and allows execution to continue seamlessly across runs.

Orchestrating multi-step workflows waiting on external systems requires setting a waiting state with waitJson to represent the external dependency. The workflow resumes with revision-checked updates once the external reply is received, ensuring conflict-safe mutations.

Preventing state conflicts when running parallel background tasks requires revision-safe lifecycle control using flow.revision. This mechanism applies conflict-checked mutations to safely create, wait, resume, finish, or cancel managed operations.

Linking multiple child tasks under a single job identity is the core function of durable flow orchestration. You run child tasks linked to the same flow id, which represents the overall job and maintains one unified owner context across all detached executions.

Detached tasks for long-running orchestration require managed lifecycle operations like createManaged, runTask, and resume to maintain state. Without persisted stateJson and waitJson, external waits or revision conflicts break the execution chain and lose progress.