Production down: deploys stuck Waiting for build slot for 3+ hours, zero active builds
bcrollins
PROOP

a month ago

Since ~14:25 UTC today (2026-07-16), every deployment for service aerolink (07ec2f8e-3e94-4476-9582-629153189af4, project 3016cc67-b330-4d1a-b26b-1fd8cadeb1f2, env production 01b0f686-7fa1-4767-8146-8f5e84702ec5) sits QUEUED with "Waiting for build slot" indefinitely. No builds are running anywhere in the workspace. Current starved deployment: 9ea0a85d (created ~17:17 UTC). Production domain aerolink.one has had no active deployment for 3+ hours (edge 404 "Application not found"). Already ruled out: usage limits (usage $20.25 vs $150 compute hard limit), billing (Pro paid, invoices settled), queue clutter (removed all stale queued deployments; a single fresh deployment still never gets a slot). Status page fully operational. Likely relevant: ~40 deployments were created in 11 minutes (14:25-14:36 UTC) by a GitHub auto-merge burst; nothing has built since — suspect stuck internal build-slot leases from that burst. Please release or reset build-slot allocation for this service or workspace so the queued deployment can build. Production is down and this is the last blocker. Thank you.

Solved

1 Replies

Status changed to Awaiting Railway Response Railway about 1 month ago


bcrollins
PROOP

a month ago

RESOLVED — closing the loop for anyone who hits this: the build queue released at ~17:31 UTC (roughly 3h10m after the wedge began). Our queued deployment built immediately, passed its healthcheck, and production has been green since 17:33 UTC. Nothing was changed on our side at the moment of release beyond what's described above (queue cleanup + config-as-code fix), so it appears the stuck build-slot allocation cleared/was cleared on Railway's side. Request for the Railway team: please still investigate why ~40 rapid GitHub auto-deploys (14:25-14:36 UTC) wedged slot allocation for 3+ hours with zero running builds — if there's an internal lease/allocation bug there, it can take down anyone with a busy merge pipeline. Happy to provide IDs/timestamps. Thanks!


Status changed to Awaiting Railway Response Railway about 1 month ago


Status changed to Solved echohack about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...