17 days ago
Hello Railway Team,
My worker service has failed to deploy twice due to an Infrastructure Error.
Project: pure-love
Service: worker
Environment: production
Region: sfo
Builder: Dockerfile
Start command: python -m scanner
The build completes successfully, but the deployment remains stuck at “Creating containers” for approximately 15–20 minutes and then fails.
Railway’s automatic diagnosis confirms that the failure occurred during container startup and was not caused by the application code. No deployment logs were generated because the container never started.
I retried the deployment once, but the same Infrastructure Error occurred again. The previous deployment is still active.
Please investigate the container startup or scheduling issue and help deploy the latest GitHub commit.
Thank you.
1 Replies
Status changed to Awaiting Railway Response Railway • 17 days ago
17 days ago
We’ve removed an older deployment that was stuck shutting down and blocking your worker’s new deployments. Your previous successful deployment remains active.
Please retry the latest deployment and let us know if it still gets stuck.
Status changed to Awaiting User Response Railway • 17 days ago
10 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 • 10 days ago