workflow

You can build durable workflows by wrapping your logic with the "use workflow" and "use step" directives to separate orchestration from business logic, then triggering the process with a start call. This enables tasks to pause, resume, and retry safely.

The best way to coordinate external-event driven flows is using durable orchestration with hooks and child workflows. This approach sustains long-running API routes and coordinates external events through crash-safe, error-tolerant execution steps.

Yes, Vercel DevKit supports crash-safe orchestration for background agents. It applies durable execution rules to pause, resume, retry, and stream outputs for multi-step processes, ensuring agents remain error-tolerant during unexpected failures.

To start a durable workflow, wrap your business logic with the "use workflow" and "use step" directives to define the orchestration steps, then trigger the execution by invoking the bundled start call within your API route.

Separating orchestration from business logic using "use workflow" and "use step" directives ensures proper serialization and streaming rule adherence. This separation maintains error-tolerant execution and allows long-running tasks to pause and resume reliably.

When structuring child workflows and hooks, you must adhere to strict serialization and streaming rules. Failing to properly isolate steps with "use step" directives can break durable execution, preventing workflows from correctly resuming or retrying after crashes.