2 months ago
My service was deploying successfully before, and the currently active deployment is still running normally.
However, new deployments repeatedly fail during the Initialization stage with:
Initialization > Snapshot code
Failed to connect before the deadline
The build itself completes successfully, including creating and pushing the Docker image, but the Deploy stage never starts.
I retried the deployment and received the same error again after approximately 7 minutes 30 seconds.
Deploy Logs are completely empty because the Deploy stage is never reached.
I also ran Railway Diagnosis, but the diagnosis itself failed.
The previous deployment of the same service is still ACTIVE and working correctly.
Could you please check whether there is an issue with the Snapshot/Initialization process for this service and advise how to resolve it?
1 Replies
2 months ago
Apologies for the trouble. We're aware of an ongoing incident, "Deployments are slow to progress," affecting deployments across all regions due to a task queue processing issue, which is causing the timeout you're seeing during the Snapshot code step. A fix is currently being rolled out. Your active deployment is unaffected. Please retry once the incident is resolved: Incident details.
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