16 days ago
The same issue as many here experience the recent times
Is there any specific reason behind it? It's not really cool that I can't rely on Railway....
4 Replies
16 days ago
During high-traffic periods, we may temporarily queue builds for Hobby tier users to prioritize Pro/Enterprise workloads, which can cause deployments to appear stuck during the build or image push phase. Queued deployments process automatically once capacity frees up, and your service currently shows a successful deployment. You can read more about this behavior in our deployment docs.
Status changed to Awaiting User Response Railway • 16 days ago
16 days ago
It doesn't show me "Limitied Access" (like docs you're pointing are saying) and... it's just stuck, for an hour in a row and no explanations are given....
Though it indeed displays "Deployment successful" - actually it's not working, just stuck on "image push". So i guess it's quite misleading text "Deployment successful" here...
Status changed to Awaiting Railway Response Railway • 16 days ago
16 days ago
Next morning it was resolved, at last. But.
Cron jobs are stuck and not executing on schedule now. Cteating a new topic on it
15 days ago
Glad the deployment issue resolved. For the cron job issue, we'll follow up in your new thread.
Status changed to Awaiting User Response Railway • 15 days ago
Status changed to Solved nico • 15 days ago