Hi,

I have a production service with a persistent volume attached in us-west2.

The currently running deployment is healthy, and both the service deployment configuration and the attached volume use us-west2.

Railway's current region documentation/API also recognizes us-west2.

However, the dashboard briefly showed:

“Invalid region us-west2 is configured on this service and is blocking deployments.”

At the same time, the UI offered US West (us-west2) as the preselected replacement.

After reloading the dashboard later, the warning disappeared without any configuration change.

The service is volume-backed and uses SQLite, so I do not want to change the region setting experimentally because I need to preserve the existing volume and avoid any migration/recreation/data copy.

Could someone confirm:

Whether this is a known dashboard/validator issue.

Whether an existing multiRegionConfig.us-west2 configuration is still valid for a volume-backed service.

Whether any normalization/change is actually required before the next deployment.

If a change is required, whether selecting the same us-west2 region preserves the existing volume without migration, recreation, or data movement.

Whether such a change triggers a restart or deployment.

I have not changed any configuration yet.