Skip to content
Legacy SFO service with attached Volume — region config unexpectedly changed to us-west2 after scale command
10projectx-ai
OP

20 days ago

Hi Railway team,

I need help with a production service that is currently healthy and running in the legacy sfo region with an attached persistent Volume also located in sfo.

I ran a Railway scale operation intended to scale the existing sfo instance to zero temporarily for a backup procedure.

Instead of simply scaling the existing instance down, the operation committed a configuration change and created a new deployment.

That new deployment failed during the build stage, so fortunately it never replaced the currently running production deployment.

The current live state is:

  • Existing production deployment: healthy
  • Current deployment region: sfo
  • Current Volume region: sfo
  • Current instance count: 1
  • Application health: HTTP 200
  • Volume remains attached and unchanged

However, after the failed scale operation, the persisted Railway service configuration now reports:

us-west2 = 1

The committed scale patch appears to have removed the legacy region using:

"sfo": null

There is no later configuration patch restoring the original region.

So the current situation appears to be:

Running infrastructure:

Service in sfo + Volume in sfo

Persisted service configuration:

us-west2 = 1

I also attempted to restore the original sfo=1 configuration, but Railway now rejects sfo as an accepted region value.

Because this is a production service with persistent data, I do NOT want to trigger a new deployment, migrate the Volume, detach/recreate the Volume, or change the service to us-west2 without guidance.

Could you please advise how to safely restore the persisted service configuration to the existing legacy sfo setup without migrating or replacing the current Volume?

I would also like confirmation on this:

If I deploy the service again while the persisted configuration says us-west2=1 but the current Volume remains in sfo, will Railway attempt to migrate the Volume or move the service to us-west2?

I have the exact Project ID, Environment ID, Service ID, Volume ID, Volume Instance ID, active deployment ID, and failed deployment ID available and can provide them privately to Railway staff if needed.

I have intentionally stopped all further deploy, scale, region, restart, rollback, and Volume operations until this is clarified.

Thanks.

Solved

1 Reply

Railway
BOT

20 days ago

Your service's saved configuration now reads US West (us-west2) with 1 replica, while the running deployment and its volume are still in the older US West location. That older location is no longer a selectable region, so there is no setting you can use to put the saved configuration back to it; the selectable regions are US West Metal (us-west2), US East Metal, EU West Metal and Southeast Asia Metal.

To your second question: yes. If you deploy with the configuration as it stands, the service is placed in us-west2, and because its attached volume lives elsewhere, the volume is migrated to us-west2 as part of that deploy. The migration can take a while depending on the volume's size and the service is down while it runs, as described in our regions guide. Until you deploy, the current deployment and volume stay where they are.


Status changed to Awaiting User Response Railway • 20 days ago


Railway
BOT

13 days ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • 13 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...