Deployments stuck in "Queued" — upstream GitHub issues
webdevtodayjason
PROOP

9 days ago

Description:

Deployments to my production service are stuck in "Queued" status with the message "Deployment queued due to upstream GitHub issues."

- The GitHub commit status was previously in an error state from a failed deploy. I've since posted a success status via the GitHub API, and confirmed there are no branch

protection rules, no failing check runs, and no GitHub Actions workflows on the branch.

- Pushing new commits (including empty trigger commits) all queue with the same message.

- The app itself is running fine on the previous deployment.

Solved

11 Replies

rashmur
PRO

9 days ago

Yes. I am seeing long queued times on new git pushes. running into 20 mins as of now. Multiple services are stuck in this queued state.


adhesikan
PRO

9 days ago

Yes I am seeing the same issue..


9 days ago

Apologies for the trouble. We're aware of an issue, "Builds and deployments are slow to progress," affecting deployments across all regions. A fix has been released and we're working through the backlog of queued builds. Your deployments should begin progressing shortly. Follow updates at https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh


Status changed to Awaiting User Response Railway 9 days ago


adhesikan
PRO

9 days ago

Great! Thanks!


Status changed to Awaiting Railway Response Railway 9 days ago


leonlindblad
PRO

9 days ago

yes I am seeing exactly the same thing this evening I am just trying to restore from a back up from yesterday but even that is taking a long time

Attachments


brody

Apologies for the trouble. We're aware of an issue, "Builds and deployments are slow to progress," affecting deployments across all regions. A fix has been released and we're working through the backlog of queued builds. Your deployments should begin progressing shortly. Follow updates at https://status.railway.com/incident/cmm2cvzx50dxkx4rz5dx8efxh

messi100000000
HOBBY

9 days ago

this happens MANY times all weeks, WHYYYY???? It's disrespectful, plus you pause hobby accounts as if they were free, we pay every month for a disastrous service


teamfreya
PRO

9 days ago

users blowing up my inbox!!!!!! come on!


phatty777
HOBBY

9 days ago

Hobby builds and deployments are paused to help clear the backlog. Fine to take our money, but not deploy our projects? I want a refund or free credits. Were still paying customers.


pollis22
PRO

9 days ago

First Claude goes down, now my deployments are stuck. What happened?


gitcagey
PRO

9 days ago

Railway, you are making it really hard to convince my clients to use vs. go on prem. Outage 2 weeks ago caused a firestorm...finally got green light to deploy something today to speed up delivery because of internal resource pinch, and deployments are stuck in queued. Fantastic!


8 days ago

We're sorry for the impact this had on your workflow, especially with the pressure you're under to deliver for your clients. We know this kind of disruption is unacceptable and we're working to make sure it doesn't keep happening.


Status changed to Awaiting User Response Railway 8 days ago


Status changed to Solved brody 8 days ago


Loading...