a month ago
Project ID: afdb73b1-5501-4db2-a869-8ed518e5837c (environment: production, 4073823c-0716-4e6d-8a6d-e55e66f488ac)
Since ~18:47 UTC today (2026-07-21), every new deployment across all ~24 services in this project sits in QUEUED and never transitions to BUILDING. Exactly one deployment briefly built (~19:40 UTC) and then the queue froze again. As of ~21:00 UTC there are 24 deployments QUEUED and 0 BUILDING.
Details:
- We upgraded this workspace to the Pro plan earlier today, so this shouldn't be Free/Hobby build-slot pausing. It's possible the upgrade hasn't propagated to the build scheduler.
- Deployments created via both GitHub push triggers and the API (serviceInstanceDeploy latestCommit: true) all stay QUEUED indefinitely.
- buildLogs for the queued deployments are empty (they never enter BUILDING), so this isn't a build failure.
- No banner or incident: status.railway.com shows fully operational, GraphQL API responds normally.
- We already cleaned our own queue: cancelled 33 stale duplicate QUEUED deployments via deploymentCancel (keeping the newest per service). Queue went 57 → 24 but still nothing builds. We have NOT been spamming redeploys.
- Example stuck deployment: service d3b07563-a7b3-4205-b425-5597ce6b3c08 (team-app), queued since 18:59 UTC.
Can you check whether the build scheduler is wedged for this project/workspace, or whether the Pro upgrade needs a manual nudge? This is blocking production deploys for our business.
4 Replies
a month ago
Your workspace is confirmed active on the Pro plan, so this is not a plan-tier build restriction. Our records show 15 deployments in this project from around 19:38 UTC that are currently RUNNING, and the latest deployment for each of your services (around 20:00 UTC) shows a status of SKIPPED, not QUEUED. A SKIPPED deployment means the build was bypassed, either because the Skipped Builds feature detected the same source code was already built, or because the deployment was superseded by another one for the same service. This would explain the empty build logs you're seeing. Could you check your dashboard now to confirm whether services are actually running from the 19:38 UTC batch, and whether you still see any deployments stuck in QUEUED? If you do still have QUEUED deployments, try triggering a fresh redeploy on a single service via the deployment menu to test whether the build pipeline picks it up.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thanks — checked. To clarify: the SKIPPED entries are expected (we use watch paths, most commits don't touch a given service). The problem is deployments that SHOULD build never leave QUEUED.
Just ran the test you suggested on one service (team-app, d3b07563-a7b3-4205-b425-5597ce6b3c08):
- Cancelled its stale QUEUED deployments so the queue for that service was empty.
- Triggered a fresh redeploy of the latest commit (via serviceInstanceDeploy latestCommit: true) at ~20:4x UTC.
- The new deployment has now been in QUEUED for 5+ minutes and never transitions to BUILDING. Build logs are empty (it never starts).
Project-wide we still see ~48 deployments in QUEUED and 0 in BUILDING. The services currently RUNNING are on images built this morning — nothing new has built since ~18:47 UTC except a single deployment around 19:40. So the build pipeline is not picking up queued builds for this project. Can you check the build scheduler for project afdb73b1-5501-4db2-a869-8ed518e5837c?
Status changed to Awaiting Railway Response Railway • about 1 month ago
Railway
Your workspace is confirmed active on the Pro plan, so this is not a plan-tier build restriction. Our records show 15 deployments in this project from around 19:38 UTC that are currently RUNNING, and the latest deployment for each of your services (around 20:00 UTC) shows a status of SKIPPED, not QUEUED. A SKIPPED deployment means the build was bypassed, either because the [Skipped Builds](https://docs.railway.com/builds/skipped-builds) feature detected the same source code was already built, or because the deployment was superseded by another one for the same service. This would explain the empty build logs you're seeing. Could you check your dashboard now to confirm whether services are actually running from the 19:38 UTC batch, and whether you still see any deployments stuck in QUEUED? If you do still have QUEUED deployments, try triggering a fresh redeploy on a single service via the deployment menu to test whether the build pipeline picks it up.
a month ago
Thanks — checked. To clarify: the SKIPPED entries are expected (we use watch paths, most commits don't touch a given service). The problem is deployments that SHOULD build never leave QUEUED.
Just ran the test you suggested on one service (team-app, d3b07563-a7b3-4205-b425-5597ce6b3c08):
Cancelled its stale QUEUED deployments so the queue for that service was empty.
Triggered a fresh redeploy of the latest commit (via serviceInstanceDeploy latestCommit: true) at ~20:4x UTC.
The new deployment has now been in QUEUED for 5+ minutes and never transitions to BUILDING. Build logs are empty (it never starts).
Project-wide we still see ~48 deployments in QUEUED and 0 in BUILDING. The services currently RUNNING are on images built this morning — nothing new has built since ~18:47 UTC except a single deployment around 19:40. So the build pipeline is not picking up queued builds for this project. Can you check the build scheduler for project afdb73b1-5501-4db2-a869-8ed518e5837c?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Good news, the backlog has cleared. Every queued deployment in your project has now built, and all services are running on the new builds as of about 21:24 UTC (one service, content-ritual-bot, was still finishing its build when I checked). Your team-app test deploy from 20:26 succeeded too.
If anything gets stuck in QUEUED again, reply here and we'll dig in right away.
Railway Team
Status changed to Awaiting User Response Railway • about 1 month ago
24 days 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 • 24 days ago