Deployments permanently stuck on “Waiting for build slot” after upgrading plan
juanramonpq-source
PROOP

2 months ago

Hello Railway team,

I am experiencing an issue where all deployments remain permanently stuck in “QUEUED” status with the message:

“Waiting for build slot”

The problem started before upgrading my subscription, but it still persists after upgrading to the $20/month plan.

Important details:

- GitHub integration works correctly

- New commits trigger deployments normally

- Deployments appear in Railway correctly

- However, builds never actually start

Project information:

- Project: poker-combat-bot

- Environment: production

- Runtime: Node.js 18.20.8

- Region: US West

I have already tried:

- cancelling queued deployments

- redeploying manually

- creating new deployments

- logging out and back in

- clearing build cache

- creating a new service

- forcing new GitHub commits

Despite all of this, deployments still remain indefinitely in “Waiting for build slot”.

Could you please check whether:

- my workspace is stuck internally,

- the new subscription has not been fully applied,

- or the build queue for my account/service is blocked?

Thank you very much for your help.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 2 months ago


2 months ago

We're aware of these transient build queue issues and are actively working on improvements.


Status changed to Awaiting User Response Railway about 2 months ago


Railway
BOT

2 months ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway about 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...