The region identifier "sfo" is not valid. The supported identifiers are us-west2, us-east4-eqdc4a, europe-west4-drams3a, and asia-southeast1-eqsg3a as listed in our regions docs. Your service "mycelia-os-fresh" is currently deployed successfully, while the copy "mycelia-os-fresh-6GVU" is in a crashed state. If the invalid multiRegionConfig was set via a railway.toml or railway.json file in your repo, updating that file to use a valid region identifier (or setting multiRegionConfig to null to clear it) and redeploying should resolve the stuck state. If you're unable to update the config through the dashboard at all, try using the Railway CLI with railway scale us-west2=1 to overwrite the region config, or remove the config-as-code file from your repo and redeploy.

We've corrected this through a couple of different paths. The regions should resolve correctly now because of changes we added in the backend, but if they aren't resolving you can fix this by going into your service, and selecting Settings and scrolling down to Scale where you should see a drop down for setting the correct region now. That will let you correct this without having to contact support. This control was added today, and if the automatic recovery didn't happen, should let you get back up and running.