# Configure where run state lives in Vercel Workflows

DevFeed: [Configure where run state lives in Vercel Workflows](<https://devfeed.tech/articles/configure-where-run-state-lives-in-vercel-workflows-874.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/configure-where-run-state-lives-in-vercel-workflows>)

Author: Pranay Prakash

Published: 2026-07-20T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [SDKs](<https://devfeed.tech/topics/sdks.md>), [incident](<https://devfeed.tech/topics/incident.md>)

Tags: [incident](<https://devfeed.tech/tags/incident.md>), [release](<https://devfeed.tech/tags/release.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [vercel](<https://devfeed.tech/tags/vercel.md>), [workflows](<https://devfeed.tech/tags/workflows.md>)

## AI overview

Vercel Workflows now stores each run's state, queue dispatch, and output streams in a single home region. Runs can use their starting region by default or a selected target region, keeping workflow execution and streaming close to users. Regional failures trigger failover to the next closest region.

## Source excerpt

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 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