taskflow

Long-running workflows persist across multiple prompts using durable flow orchestration that maintains a single owner context. This approach uses stateJson persistence and revision-checked mutations to preserve coherent return states between prompt sessions.

Durable task orchestration automates multi-step jobs with fault tolerance and pause/resume capabilities. You need it for software engineering tasks and plugin development when workflows must survive beyond a single prompt execution and maintain coherent state.

To resume a paused multi-step job after a failure, the orchestration system tracks currentStep and waitJson states to restore execution. It supports finishing, failing, waiting, canceling, and resuming workflows through revision-tracked mutations.

Yes, you can manage child tasks linked to a parent workflow using child-task linkage features. The system persists stateJson for both parent and child tasks while maintaining owner session context across the entire workflow hierarchy.

The best way to handle owner session context in long-running jobs is using owner-scoped task orchestration. It preserves a single owner context across prompts while managing flow identity and state persistence through revision-checked mutations.