Hey there! We've found the following might help you get unblocked faster:

• 🧵 Deployments stuck in "Queued. Waiting for deployment slot"

• 🧵 Deployment get stuck in "Queued"

• 🧵 Deployment stuck in queued

If you find the answer from one of these, please let us know by solving the thread!

Hello Railway Support Team,

I'm experiencing a critical deployment issue with my project that has been ongoing for the past 2 days.

Issue:

My deployment is stuck with the status "waiting for deployment slot" and won't proceed. This is blocking all

my development work as I need to deploy multiple times per day.

Project Details:

- Project: Watni Digital

- Environment: production

- Service: watnidigital-api-backend

- Issue Duration: 2+ days

- Impact: Unable to deploy any updates

What I've tried:

- Waiting for the deployment to complete naturally

- Checking project quotas and limits

- Verifying build configuration

Request:

Could you please:

1. Check if there's a deployment queue issue on your end

2. Clear/reset my deployment slot if stuck

3. Allow my deployment to proceed

This is affecting my production service and I have users waiting for updates. Any help would be greatly

appreciated!

Thank you for your assistance!

Hi there,

We had an issue with deploys (https://status.railway.com/cmgpc8epg00e2vt5jhwjfda9l) that has since been resolved.

A redeploy should resolve this.

Best,

The Railway Team

Hello Railway Support Team,

Thank you for your earlier assistance regarding the “waiting for deployment slot” issue in my project. Unfortunately, the same problem has reappeared, and deployments are once again getting stuck at the same stage.

It seems the previous fix did not permanently resolve the issue. Could you please review this again and help ensure a stable fix so deployments can proceed normally?

Thank you for your prompt support.

Best regards,
Muhammad Arshad Awan
Project: Watni Digital
Service: watnidigital-api-backend

Hello,

Upon further inspection, the original issue you are currently facing is not due to an incident or platform malfunction, but rather a misconfiguration on your end.

You have set your pre-deploy command to start Uvicorn. You should not be starting your main application in the pre-deploy step.

Please remove that command from the pre-deploy step and move it to the start command.

You will also need to manually cancel any hanging deployments as a result of this misconfiguration.

Best,
Brody