Configure where run state lives in Vercel Workflows
By Steven Van ·
Runs keep their state, queue dispatch, and streams in one region for their lifetime, with automatic failover during regional incidents.
Vercel Workflows now pins each run to a single home region for its lifetime, keeping its state, queue dispatch, and output streams together, as described in the Workflows documentation. By default that region is wherever the run starts, but a specific target region can be chosen instead. For an agent built on Workflows, this keeps the whole loop close to the user: an agent serving someone in Sydney executes, checkpoints its progress, and streams output from Sydney. During a regional incident, workflow traffic fails over to the next closest region.
- Pin a run to a chosen region by passing a region option to the start function.
- Requires updating the Workflow SDK to workflow@5.0.0-beta.33 or later.
- Existing workflows pick up regional placement automatically on their next run, with no migration or code changes.
Diagram of how a Vercel Workflows run keeps its state in one home region.
Diagram of how a Vercel Workflows run keeps its state in one home region.
Vercel
The platform for frontend developers — deploy, preview, and scale web apps and AI agents with zero config.
View Vercel →