3 months ago
I have been unable to build anything on railway for the last few hours. I am stuck on "Queued. Waiting for deployment slot" everytime I try to push something. This is getting urgent because we need to deploy hotfixes for our service. I saw a lot of similar posts recently all of which needed to be solved by the railway team. Is there anything we can do to solve this quickly ?
8 Replies
3 months ago
Hi! I will escalate this to the team.
3 months ago
!t
3 months ago
This thread has been escalated to the Railway team.
Status changed to Awaiting Railway Response medim • 3 months ago
3 months ago
Thanks !
3 months ago
Have been having the same issue today. I have an ongoing pending queue on one of the services going 4 hours now. Deployment id: ef25beda-8c9b-4bac-9751-c4545a7d173d
Hey guys do you have any update on this? We have a critical bug fix that we need to deploy asap and this is completely blocking for us
3 months ago
We are currently taking a look. Can you please provide links to deployments that are stuck
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
We had a change go out today that in a rare case could cause deploys to get stuck in queued state. The root cause has been fixed, but if you still see some stuck deployments, please share here.
3 months ago
@Noé @nion Can you confirm that your deployments are going through?
3 months ago
I have faced same issue. Deployment Id: 82ffc0dc-2ff3-426c-882a-ff24587dfda6
Status changed to Awaiting Railway Response Railway • 3 months ago
ayberkcal
I have faced same issue. Deployment Id: 82ffc0dc-2ff3-426c-882a-ff24587dfda6
3 months ago
I don't see any stuck deployments for you. The deployment ID you provided is failing to start with a different error related to the Dockerfile.
unable to find user root # allow writing to Railway-mounted volume: no matching entries in passwd file"Please open up a new help thread if you are still experiencing issues deploying
Status changed to Awaiting User Response Railway • 3 months ago
Yes all good for now. What was the origin of the problem ? Anything we can do to make sure this does not happen again ?
3 months ago
As Jr said in the help station thread: "We had a change go out today that in a rare case could cause deploys to get stuck in queued state. The root cause has been fixed, but if you still see some stuck deployments, please share here."
3 months ago
My deployments seem to have been resolved also, thx
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
This should be resolved now. There may have been some delayed deploys around that time and 2 hours ago in US East.
Status changed to Awaiting User Response Railway • 3 months ago
Status changed to Solved ray-chen • 3 months ago
3 months ago
!s