Vercel Workflows 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.
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 Workflow SDK to
To pin a run to a specific region, pass the
Existing workflows pick up regional placement on their next run, with no migration or code changes.
Learn more in the Workflows documentation.
Read more
Continue reading...
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 Workflow SDK to
workflow@5.0.0-beta.33 or later:To pin a run to a specific region, pass the
region option to start():Existing workflows pick up regional placement on their next run, with no migration or code changes.
Learn more in the Workflows documentation.
Read more
Continue reading...