6 hours ago
Service: soldoutzero-collector (Project 297efd8d-c596-4b9e-83ff-a84f11169498, Service e8531f7d-9bec-4bfe-ab14-56b6cdd93518, region US West, Dockerfile builder, Hobby plan)
Since 2026-09-17 01:01 UTC every build fails at "Build > Build image" after ~15 seconds. Build context uploads fine (unpacking archive 770 KB, uploading snapshot 232.8 KB), then:
Build Failed: build daemon returned an error < NotFound: forwarding Ping: no such job 7ce6d717-4a6c-46e2-8551-25b07183e735-20260917010118 >
scheduling build on Metal builder "builder-bvqbzi"
Failed attempts (UTC): 01:01 (new commit), 01:12 (redeploy), 01:23 (empty commit, new build job), 02:55 (redeploy).
Railway's built-in Diagnosis reports "Infrastructure Error: internal build scheduling error, not a problem with your code or configuration."
The previous deployment (commit 82cb837, same Dockerfile) built successfully on 2026-09-16 and is still running. The only change since is one .ts file; the Dockerfile does not even compile TypeScript, so the failure happens before any of our code is read. There is no "Enable metal build environment" toggle in this service's settings, so I cannot switch builders myself.
Could you check the builder assigned to this service, or move it to a different build environment? Thank you.
3 Replies
Status changed to Awaiting Railway Response Railway • about 6 hours ago
5 hours ago
Update: I created a fresh service in the same project from the same repo and commit, with no variables or volume. It built successfully in about a minute and started (then exited only because env vars were missing). So the repo and code are fine — the original service (e8531f7d-…) appears to be pinned to a broken builder. Every attempt on it (6 so far, including with NO_CACHE=1) is scheduled on "builder-bvqbzi" and fails in 15s. Could you re-assign that service to a different builder? I would prefer not to recreate it because it has an attached volume with login sessions.
4 hours ago
We’ve taken the affected builder out of rotation. Please retry your failed deployment and let us know if it still fails.
Status changed to Awaiting User Response Railway • about 4 hours ago
sam-a
We’ve taken the affected builder out of rotation. Please retry your failed deployment and let us know if it still fails.
3 hours ago
Redeployed and it built successfully on a different builder. Thank you for the quick fix!
Status changed to Awaiting Railway Response Railway • about 3 hours ago
Status changed to Solved Railway • about 3 hours ago