Hi Railway team,

We are on the Pro plan and our production deployment is stuck queued with “Waiting for build slot”.

Project: active-away-booking-system

Environment: production

Service: activeaway-booking-system

Deployment ID: ddf76ec9-59dd-43f1-a7a1-c9b331d08adb

Commit: 4efa0734a5f49176361fc4be3118c0840586c26c

Status: QUEUED

Queued reason: Waiting for build slot

Context:

- This is the only active non-terminal deployment in the project.

- We removed cron GitHub deployment triggers to avoid fan-out builds.

- Staging queued deployment was cancelled so production is not blocked by our own staging queue.

- We also checked other projects in the same Railway workspace; there are no other active queued/running deployments.

- The previous production deployment is still online, but latest commit is not live because this deployment has not been assigned a build slot.

- We recycled one earlier stuck queued deployment after the public incident showed resolved, but the fresh deployment is still waiting for a build slot.

Can you please check whether this deployment/workspace is stuck in the builder queue or affected by residual backlog from the Build Machines incident?