The provisioning issue that left those deployments stuck without a build has cleared. The three that hung are still showing the old initializing state, but every deployment you triggered after that point moved past initializing, got a build assigned, and ran. A fresh redeploy from your latest commit will get a build normally now, so go ahead and trigger one. If a new deployment still does not get past initializing, reply here and we will take another look.

Thanks Angelo. Unfortunately fresh deploys from the latest commit still get stuck.

Today (June 22) I triggered two new deployments from the latest commit:

• 86843a3e (via railway redeploy --from-source)
• b583862b (via a fresh GitHub push)

Both have been sitting in INITIALIZING for several minutes with no build assigned

(railway logs --build -> "Deployment does not have an associated build") — same

symptom as before.

Note: the f4a1761 deployments that did get a build and then failed were an older

commit (before I added railway.json forcing the DOCKERFILE builder), so those

failures were expected. The current latest commit has railway.json -> DOCKERFILE.

Could you take another look at why new deployments for this service still aren't

getting a build assigned? Thanks!

Thanks for the new deployment IDs. That confirms the no-associated-build issue did not fully clear for this service.

We now have the current stuck deployments to investigate:

• 86843a3e from railway redeploy --from-source
• b583862b from the fresh GitHub push

Since both are still stuck in INITIALIZING without a build assigned, this needs another look at the deployment orchestration for this specific service/source. We will check why those new deployments are not receiving build records and follow up here.

Hi, following up — it's been 2 days and the deployment is still stuck. b583862b

(the fresh GitHub push from the latest commit) has been sitting in INITIALIZING

since June 22 with no build assigned, and 86843a3e was auto-removed. The issue

has not cleared on its own.

This service has now been unable to deploy for ~5 days. Could you share any update

on the deployment-orchestration investigation, or manually re-trigger provisioning

for this service? Happy to provide anything else you need. Thanks!

Thanks for staying on this, and sorry it has dragged on. You have ruled out everything on your side correctly, and we can confirm the holdup is not your build config or your repo. New deployments for this service are not being assigned a build, which is on us to clear, not something a further redeploy from your end will fix. We are getting an engineer on the specific service so the stuck deployment gets a build dispatched and starts running. We will follow up here as soon as it moves, and we will not need anything further from you in the meantime.

Same issue here.

It's now been 3 days since you mentioned assigning an engineer, and the deployment

(b583862b) is still stuck in INITIALIZING — this service has been unable to deploy

for a full week. Is there any progress on getting a build dispatched?

If a fix will take longer, would recreating the service from scratch help, or is that

likely to hit the same orchestration issue? I'd rather not lose more time. Thanks.

Can you try cancelling the stuck deploy and doing a new one?