Configure where run state lives in Vercel Workflows
Vercel Workflows now allows you to configure which region stores each run's state, queue dispatch, and output streams, with automatic failover to the nearest region during incidents. Specify a target region using the region option in start(), and existing workflows automatically adopt regional placement on their next run.
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 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.
To get started, update the to or later:Workflow SDKworkflow@5.0.0-beta.33
To pin a run to a specific region, pass the option to :regionstart()
Existing workflows pick up regional placement on their next run, with no migration or code changes.
Learn more in the .Workflows documentation
Source: original entry ↗