10 months ago
All of a sudden I received an email saying that the deployment has failed.
When I check the dashboard I saw this error.
Region 0 is not available. Available regions are: [asia-southeast1, asia-southeast1-eqsg3a, europe-west4, europe-west4-drams3a, us-east4, us-east4-eqdc4a, us-west1, us-west2]
After checking settings I noticed that the region information was cleared.
I reselect the region and deployed again but it's still not deploying.
9 Replies
10 months ago
The same, having
"Cannot create code snapshot right now, please review your last commit or try again
If this error persists, please reach out to the Railway team." Now
10 months ago
Same here!
10 months ago
we got the same problem
10 months ago
Hey all,
We're looking into it. We were moving workloads via a Railway-initiated deploy. It seems like we rolled out some deployment config that changed the key to "Region 0"
We're working on a fix and will keep you updated.
Status changed to Awaiting User Response Railway • 10 months ago
10 months ago
Okay- update, posted this in Discord, now here.
Railway sparingly moves workloads around as a function of our ability to handle capacity. Box gets full, we move 'em. Box needs an upgrade? Move 'em.
This time, we did a type change on how we handle multi-region deployments because we need to keep track of regions across cloud providers GCP <-> Railway Metal
However, because we didn't account for that, we sent you to a new, un-working region: Region 0
Moving forward, we will:
Put a Railway banner whenever the platform takes an action on their behalf. Avoiding confusion if we do a restart.
Not send them to Region0
Since these workloads are on Metal, we have been preparing storage pools for our upcoming GA for volumes. We did these upgrades without a hitch in the past, but got caught here. We duly apologize.
angelo-railway
Okay- update, posted this in Discord, now here.Railway sparingly moves workloads around as a function of our ability to handle capacity. Box gets full, we move 'em. Box needs an upgrade? Move 'em. This time, we did a type change on how we handle multi-region deployments because we need to keep track of regions across cloud providers GCP <-> Railway Metal However, because we didn't account for that, we sent you to a new, un-working region: Region 0 Moving forward, we will:Put a Railway banner whenever the platform takes an action on their behalf. Avoiding confusion if we do a restart.Not send them to Region0Since these workloads are on Metal, we have been preparing storage pools for our upcoming GA for volumes. We did these upgrades without a hitch in the past, but got caught here. We duly apologize.
10 months ago
Thanks for the reply. Discord is banned in my country so I cannot follow there.
Does this mean it should be working now?
Status changed to Awaiting Railway Response Railway • 10 months ago
Status changed to Awaiting User Response Railway • 10 months ago
angelo-railway
New deploys are going out normally, yes.
10 months ago
Okay redeploying from the failed deployment wasn't working but it works from the running one. Looks like all good now. Thanks again.
Status changed to Awaiting Railway Response Railway • 10 months ago
Status changed to Awaiting User Response Railway • 10 months ago
Status changed to Solved angelo-railway • 10 months ago

