Workflow Durable Execution

Key takeaways

• AI tasks that outgrow request lifetimes need durable execution rather than fragile background promises.
• Workflow fits human approval pauses, long research across timeouts, multi-step automation with safe retries, scheduled reports, and external-event continuation.
• Design steps to be idempotent, store task state in durable records, and separate analysis steps from side-effect steps.
• Add approval gates before irreversible actions, and define retry, timeout, compensation, and escalation behavior before production.

Workflow 5 migration checks

The npm latest checked on 2026-10-23 is workflow@5.2.3. Preserve workflow/step boundaries and review these changes:

• runStep is removed; call the step function directly.
• getWorld(), getWorldHandlers(), and createWorld() are async. Await them in self-hosted worker bootstrap.
• Hook metadata from getHookByToken() or resumeHook() is a Promise.
• Replace removed experimental_setAttributes with setAttributes.
• Duplicate step/workflow IDs fail the build; custom bundle and route integrations need the v5 migration review.

Pass AbortSignal into steps to cancel cooperative in-flight work. A step ignoring the signal can finish, and cancellation does not reverse a completed payment or message. Keep idempotency keys and approval checks independent of token retention or force takeover.

Workflow 5 changes.

AI tasks often outgrow request lifetimes. Research, approvals, retries, external events, and multi-step actions need durable execution rather than fragile background promises.

Workflow Fits

Step Design

• Make steps idempotent when possible.
• Store task state in durable records.
• Separate analysis steps from side-effect steps.
• Add approval gates before irreversible actions.
• Emit progress and final artifacts for review.

Failure Rule

Every workflow should define retry, timeout, compensation, and escalation behavior before production.