22 days ago
It seems bugged 2+ minutes proccessing deployment stuck grey
9 Replies
22 days ago
Both recent deployments on this service show as completed, and the service is actively handling requests. The grey "processing" state you saw was likely a brief queuing delay that resolved on its own. If you trigger a new deploy and it gets stuck again, try cancelling it from the deployment's options menu and redeploying.
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
huge bug nothing is proccessing. I got clients gotta hot fix
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Your service is currently running and actively processing requests as of 15:43 UTC. Both deployments on this service completed successfully. If the dashboard still shows a grey "processing" state, try a hard refresh of the page (Ctrl+Shift+R or Cmd+Shift+R), and to push your hotfix you can trigger a new deploy by pushing a commit to your linked branch or using the redeploy option from the deployment's three-dot menu.
Status changed to Awaiting User Response Railway • 22 days ago
Railway
Your service is currently running and actively processing requests as of 15:43 UTC. Both deployments on this service completed successfully. If the dashboard still shows a grey "processing" state, try a hard refresh of the page (Ctrl+Shift+R or Cmd+Shift+R), and to push your hotfix you can trigger a new deploy by pushing a commit to your linked branch or using the redeploy option from the deployment's three-dot menu.
22 days ago
MR BOT YOUA RE WRONG! I merged and posted to my testing place and both are stuck grey. massive railway issue!
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
Hey there, sorry for the trouble, the gray likely means it's queued. It appears as though there may be upstream GitHub issues affecting build speed and queue times.
Status changed to Awaiting User Response Railway • 22 days ago
dev
Hey there, sorry for the trouble, the gray likely means it's queued. It appears as though there may be upstream GitHub issues affecting build speed and queue times.
22 days ago
Usually its fast it seems its taken 12 minutes to hit initiation stage
Status changed to Awaiting Railway Response Railway • 22 days ago
22 days ago
To correct our earlier messages, your new deployments are indeed stuck in the build stage - production since 15:38 UTC and Testing Center since 15:36 UTC. Your existing live deployment is still serving traffic, so your clients are not affected by an outage right now. The extended build times may be related to upstream GitHub issues as noted above. You can cancel the stuck deployments from the deployment's three-dot menu and try redeploying.
Status changed to Awaiting User Response Railway • 22 days ago
garrettmendelsohn
Usually its fast it seems its taken 12 minutes to hit initiation stage
22 days ago
yea until the upstream GitHub issues are resolved builds are going to be slow unfortunately, once the issues are resolved builds will go back to normal speed
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
22 days ago
My project is also stuck in build stage. For more than 10 minutes now. Usually it is really fast it takes like 2 minutes the moment I update my code in github.
Status changed to Awaiting Railway Response Railway • 22 days ago
Status changed to Awaiting User Response Railway • 22 days ago
Status changed to Solved Railway • 22 days ago
