a month ago
Hello,
I have a deployment that has remained in DEPLOYING for more than 5 hours.
Project:
perfect-surprise
Project ID:
6b59c9e6-8dad-4e56-ba92-557f7978b2c5
Environment:
acceptance
Environment ID:
37f8efd4-2c94-4bfa-afe2-a068229f1265
Service:
wireframe-generator-acceptance
Service ID:
452eb7c9-5403-4d91-841c-d5eb3de4a98a
Stuck deployment ID:
88b14c34-fc9d-48a0-bfc2-32a9533a0a3d
Created:
2026-08-29T01:16:15.058Z
Build completed successfully and the image was pushed.
Deploy logs show:
Starting Container
Next.js 16.2.1
listening on port 8080
Ready in 76ms
no process exit
no crash loop
The container has appeared healthy since approximately:
2026-08-29T01:59:35Z
However the deployment is still reported as DEPLOYING, and the previous successful deployment
77be4a29-4660-4553-bb70-bc6d5736a78f
is still serving traffic.
There is no Railway healthcheck configured (healthcheckPath: null).
The public URL currently returns HTTP 200 and /api/status returns 200 / mockMode:false, but these requests appear to still be served by the previous deployment.
This deployment started during the current/ recent Railway deployment-delay incident.
Could you please check whether this deployment is stuck in Railway's rollout/finalization state and advise whether it is safe to cancel and redeploy, or whether Railway can finalize/recover it server-side?
I have intentionally not cancelled or retried the deployment yet to avoid creating additional queued deployments.
Thank you.
1 Replies
a month ago
Apologies for the trouble. We had an incident affecting deployments across all regions ("Deployments slow to start"), which has since been resolved. Your deployment completed all its build and container steps during the incident window but the final rollout transition never fired, which is why it remains stuck in DEPLOYING while the previous deployment continues serving traffic. It is safe to cancel the stuck deployment and redeploy now that the incident is resolved. You can see the full timeline here: Deployments slow to start.
Status changed to Awaiting User Response Railway • about 1 month 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