taskflow

You orchestrate multi-step workflows by creating a managed flow that tracks flow identity and an owner session. This preserves a single owner context across detached tasks while handling child-task linkage and waiting states.

State management for long-running workflows uses revision-checked mutations and persistent stateJson. This ensures safe updates and consistent context recovery across restarts, retries, or multiple prompts.

You manage task lifecycles using setWaiting and resume methods to pause and continue execution. This handles waiting states for child tasks, allowing the parent workflow to resume seamlessly once dependencies finish.

No, this approach enforces a clear separation between orchestration and business logic. Conditional decisions and business rules remain in the caller, while the orchestration layer strictly handles flow control and state transitions.

Yes, plugin-based orchestration is fully supported for coordinating detached tasks. It utilizes revision-checked mutations to prevent conflicting updates, ensuring safe state transitions when multiple plugins or tools interact with the same workflow.

You should avoid centralized orchestration when tasks are purely independent and lack a shared owner context. If work does not require child-task linkage, waiting states, or revision-checked mutations across steps, simpler stateless execution is more appropriate.