a month ago
Hi,
My project is repeatedly failing during the build phase before any useful build logs are produced.
The repeated error is:
Build Failed: build daemon returned an error < failed to receive status: rpc error: code = NotFound desc = no such job ... >
Recent job examples:
- 26268872-fe52-44ac-b9a7-7c3351e3cc29-20260514120145
- 21bbabff-478f-4578-9aec-a06f418d4653-20260514115921
- cf7ca342-30e9-43be-9d5f-ccd4df5c9b00-20260514115453
This happened first with Nixpacks, and then again after switching the service to a Dockerfile builder.
The app itself builds locally with:
npm run build
The repository currently has:
- Node pinned to 20.x in package.json
- .nvmrc set to 20
- railway.toml set to builder = "DOCKERFILE"
- dockerfilePath = "Dockerfile"
- Dockerfile present at the repo root
The latest commit I’m trying to deploy is:
5c068ae51f020fb9a958df313602cacbc8f6f2db
Could this be a Railway builder/Metal builder issue? The failure appears to happen before the build job returns normal Docker or npm logs.
Thanks.
4 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This wasn't your config, it was a build infrastructure issue on our side. We've mitigated it. Please trigger a fresh deploy and it should build cleanly.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Why wasn't an incident declared?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
I am having the same issue:
The build failed due to a transient infrastructure problem where the build daemon lost track of the job, returning an RPC "no such job" error before any build steps could execute. Three consecutive builds on May 14 all failed with the same error on the same builder node.
a month ago
Why deployments are triggering on my railway dashboard after pushing stuff to the repo ? its been 30 minutes and tried a few times
Status changed to Solved clinicalcme • about 1 month ago