Configure where run state lives in Vercel Workflows
Vercel has announced a new feature for Vercel Workflows that enables developers to configure the home region for each run's state, queue dispatch, and output streams. By default, the home region is the region where the run starts, but developers can specify a target region using the `region` option passed to `start()`. This ensures that for agents built on Workflows, the entire execution loop stays near the user—for example, an agent serving someone in Sydney executes, checkpoints its progress, and streams output from Sydney. During a regional incident, workflow traffic automatically fails over to the next closest region. To use this feature, the Workflow SDK must be updated to version `workflow@5.0.0-beta.33` or later. Existing workflows will automatically pick up regional placement on their next run without requiring migration or code changes. Vercel's changelog emphasizes that a run keeps its home region for its lifetime, providing consistency and low-latency execution for geographically distributed users.
Developers can now reduce latency by pinning workflow runs to specific regions, with automatic failover during incidents.