2 months ago
A production deployment has been stuck in INITIALIZING and never creates an associated build. When I request build logs, the CLI reports:
Deployment does not have an associated build
A second deployment attempt behaved the same way. The previous successful deployment is still serving traffic.
I see the active Railway incident concerning slow or stuck deployments. Will affected deployments resume automatically after recovery, or should I cancel them and redeploy once the incident is resolved?
1 Reply
2 months ago
Probably safest bet is to just cancel them and redeploy when the incident is resolved unless you have some reason not too. But I'm also not a railway representative.
Status changed to Awaiting User Response Railway • about 2 months ago
a month 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 • about 1 month ago
