Configure where run state lives in Vercel Workflows
Vercel just gave AI agents a latency superpower: run state now lives in your user's region, not a distant data center.
Why it matters
Vercel Workflows now allows developers to pin agent execution and state to specific regions, reducing latency for geographically distributed users and improving resilience during regional outages. For AI agents, this means faster inference loops and better user experience.
The key facts
12 to knowVercel Workflows SDK updated to workflow@5.0.0-beta.33 or later
Run state, queue dispatch, and output streams now co-located in single home region
Region can be explicitly chosen via region option in start() or defaults to run origin
Regional failover to next closest region during incidents
No migration required for existing workflows
Latency optimization for agent-based applications serving geographically dispersed users
Run state, queue dispatch, and output streams now collocate in a single home region
Agents can be pinned to specific regions via regionstart() option
Regional placement requires SDK update to workflow@5.0.0-beta.33 or later
Existing workflows pick up regional placement on next run with no migration needed
Automatic failover to next closest region during regional incidents
Use case: agent serving Sydney user executes, checkpoints, and streams from Sydney
Go to the source
Vercel Blogvercel.com
Publisher excerpt: now keeps each run's state, queue dispatch, and output streams in a single home region: the region where the run starts by default, or any target region you choose.Vercel Workflows A run keeps its home region for its lifetime, so for agents built on Workflows, the whole loop stays near the user: an…