Workflow SDK 5: built for production
Workflow SDK 5 adds per-run payload encryption, regional state and fewer queue hops. Builders running long-lived agents can use it for durable runs, but should account for key management and where run data resides.
Workflow SDK 5 encrypts run payloads with **AES-256-GCM** and a unique key per run. Vercel manages keys by default; self-hosted Worlds must provide a stable 32-byte key. Runs now keep state in their starting region, and measured workloads showed **1.6× to 25×** latency and overhead improvements over v4.
For agent loops with many steps, tool calls or streams, consider whether durable workflows would make interruptions recoverable and reduce per-step overhead. Set a run’s region near its database or data residency boundary, and use payload retention settings if completed-run contents should be deleted.
Workflow SDK 5 encrypts run payloads with **AES-256-GCM** and a unique key per run. Vercel manages keys by default; self-hosted Worlds must provide a stable 32-byte key. Runs now keep state in their starting region, and measured workloads showed **1.6× to 25×** latency and overhead improvements over v4. For agent loops with many steps, tool calls or streams, consider whether durable workflows would make interruptions recoverable and reduce per-step overhead. Set a run’s region near its database or data residency boundary, and use payload retention settings if completed-run contents should be deleted. The retention option is experimental. Run attributes are searchable but stored in plaintext, and v4 runs remain in iad1; failover does not move a run’s state from its home region.
Workflow SDK 5 makes durable agent runs more practical by reducing measured overhead, encrypting run payloads, and keeping state in the starting region. Its regional and retention constraints matter to recovery and data handling, while plaintext searchable attributes and the experimental retention option limit the privacy guarantees that can be inferred.