an hour ago
Hello Railway Support,
My service CT-Market-backend is connected to GitHub repository abhitadmali7800-creator/CT-Market-backend, branch main, with auto-deploy enabled.
My latest commit d147cff has been pushed successfully, but the deployment has remained in QUEUED status for over 20 minutes. No build or deploy logs are appearing.
The previous deployment is still active, but the new API route /api/delivery/admin/list returns:
{"success":false,"message":"Route nahi mila."}
I also noticed the Railway status page showing degraded performance after the October 21 incident.
Could you please investigate why my deployment is stuck in the queue and help me deploy the latest commit?
Thank you.
2 Replies
an hour ago
Your new deployment of CT-Market-backend has been sitting in QUEUED since 07:49 UTC. Until a new deployment finishes, your previous successful deployment keeps serving traffic, which is why the new /api/delivery/admin/list route isn't available yet.
To start a fresh deployment of the latest commit, open the service, press Cmd+K (Ctrl+K on Windows) and choose Deploy Latest Commit, or push a new commit. If that build fails right after it starts, it can be retried once.
The Elevated Build Failure Rate incident from yesterday has been resolved, and builds are processing normally across all regions: incident details.
Status changed to Awaiting User Response Railway • about 1 hour ago
24 minutes ago
Thanks for your report and apologies for the hassle. We have diagnosed the issue and engineers will look at a fix shortly. Will update.