a month ago
Service: SportzTrakr (d0f8db78-d26f-4006-95a5-69b520272ebb)
Project: SportzTrakr (9cd822af-2f6f-4c8b-92d2-444222dcd896)
Environment: production (9ab66165-4855-4e77-b389-d933ff8c6810)
Region: us-east4-eqdc4a, 1 replica
Three consecutive production deploys are stuck in WAITING and never transition to BUILDING (empty build + deploy logs, zero activity):
- d62d75e8-8ff6-4d53-b02f-c162077171e1 (02:03:51Z) SKIPPED after ~12 min
-
- 91371f0a-76d7-4208-a00e-4e2e368af316 (02:17:50Z) SKIPPED
-
- 14fad13d-996e-419f-9be6-8b0f0401f551 (03:02:22Z) currently WAITING
The previous successful deploy (09d18790-9eaf-481b-9514-84eb91639241) is still serving live traffic fine. Re-triggering via fresh commits to the prod branch reproduces the wedge every time.
This matches the known deploy-queue deadlock bug (a previous deploy not releasing its queue slot), same symptom as threads deploys-stuck-in-queued-build-never-sta-e975c789 (Jun 26) and development-service-stuck-in-queued-depl-93489e13 (Jul 11-12). Please manually release the stuck deploy-queue slot for this service. Once cleared, our latest commit (2cc5fe5a on the prod branch) should build and go live. Thank you!
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Good news, this wasn't the queue deadlock and there's nothing stuck to release. Your service has "Wait for CI" turned on, so each deploy sits in WAITING until GitHub's check suite finishes. The two that "wedged" were actually SKIPPED because their CI check suite failed (7fecf855 and 172faae9). Your latest commit 2cc5fe5a passed CI, built, and is live now on www.sportztrakr.com.
If you'd rather deploys not block on CI, you can turn off "Wait for CI" in the service's settings under the GitHub trigger.
Railway Team
Status changed to Awaiting User Response Railway • about 1 month ago
Status changed to Solved sam-a • about 1 month ago