a month ago
A configuration deployment has remained INITIALIZING for more than two hours. Its Build Logs show only 'Waiting for build to start...'. A previous related deployment completed its cached Docker build and image push, then was marked Failed without an application compile error. The current production deployment is Active and must remain online. Railway documentation says an initializing deployment should offer 'Abort deployment', but the action menu offers only 'Remove', whose confirmation warns it will immediately go offline. What is the safe way to cancel only the stuck initializing deployment without affecting the current Active deployment? No secrets, customer data, deployment IDs, or raw logs are included.
1 Replies
a month ago
The stuck INITIALIZING deployment is not your active production deployment, so using "Remove" on it will only cancel that specific stuck deployment and move it to history. It will not take your currently serving deployment offline. The "Remove" warning applies when removing an active (running) deployment, which is not the case here. After removing it, the build/deploy slot it is holding will free up.
Status changed to Awaiting User Response Railway • 28 days ago
21 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 • 21 days ago