a year ago
My container name is Backend API on development environment
Region: US West
It runs a python server based on Fast API.
Today, it has failed to deploy due to timing out in the deployment phase.
We have tried deploying previously successfully deployed code with the same issue occurring
Effect: Blocking staging environments and hotfix ability for our app.
7 Replies
10 months ago
Hello,
Please confirm that me and my teammates can view your project for the duration of this thread.
Status changed to Awaiting User Response Railway • 11 months ago
brody
Hello,Please confirm that me and my teammates can view your project for the duration of this thread.
10 months ago
confirmed
Status changed to Awaiting Railway Response Railway • 11 months ago
10 months ago
Would you be interested in migrating this this environment to Metal? it looks like we are running out of capacity on GCP and won't be adding more, so Metal would be the path forward here.
Status changed to Awaiting User Response Railway • 11 months ago
brody
Would you be interested in migrating this this environment to Metal? it looks like we are running out of capacity on GCP and won't be adding more, so Metal would be the path forward here.
10 months ago
Yes would love to. How do I proceed?
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Awaiting User Response Railway • 11 months ago
10 months ago
This is disrupting our services quite a bit. An unplanned migration which led to downtime for an enterprise level client like us is not acceptable.
Given the seriousness of the situation, can we get dedicated support with this migration ASAP?
Status changed to Awaiting Railway Response Railway • 11 months ago
10 months ago
Hello,
You can switch the region in the service settings, which will deploy it to a Metal region with much more capacity.
Make sure you have the Metal Volumes feature flag enabled for that -
Status changed to Awaiting User Response Railway • 11 months ago
7 months 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 • 7 months ago
