8 days ago
My deployments have been failing consistently with the following error:
"Build Failed: build daemon returned an error < failed to receive status: rpc error: code = NotFound desc = no such job >"
The Railway automatic diagnosis confirmed it is an infrastructure error and states "no code or configuration changes are needed". The build fails at the "Build > Build image" step in ~25 seconds, before any build steps execute.
This has happened on 4+ consecutive deploys. Redeploying does not resolve the issue.
8 Replies
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
Same problem here.
8 days ago
Same error pattern here. trustbench.io service:
- 4 consecutive failed deploys 12:47–13:06 UTC
- All on builder-wkkdbn (Metal builder)
- Identical "Build Failed: build daemon returned an error < failed to receive
status: rpc error: code = NotFound desc = no such job >"
- Same death point: after "unpacking archive" completes, before any compilation
- Same ~25s elapsed before failure
- No code/config changes from prior successful builds earlier today
Deploy IDs: 52a993dd-0a2e-4f95-9fca-f33a1017411c, a75a242f-9db3-4849-b482-2b64464e0f0c, 0944256c-b45c-46c3-92c8-5254249c360b
If you're seeing builder-wkkdbn in your own logs too, that's a stronger
signal for Railway. If different builder, the issue is broader than one
builder pool.
8 days ago
- Failed deployments: a90bbd15, f38d79ce, 12c2916e
- Builder: builder-wkkdbn
- Error: RPC "no such job" on BUILD_IMAGE stage
- Pattern: 4+ consecutive failures, same builder instance
- Last success: 9dea60fb (~7 hours prior)
Same thing for me.
8 days ago
exact same thing here
8 days ago
same
8 days ago
same here
8 days ago
Confirmed across all of you, this was a build infrastructure issue on our side affecting multiple services this morning. We've mitigated it. Please trigger a fresh deploy for your affected services and it should go through.
Status changed to Awaiting User Response Railway • 8 days ago
8 days ago
Confirmed, fresh redeploy went through cleanly. Thanks for the quick mitigation and the follow-up. All good on my end.
Status changed to Awaiting Railway Response Railway • 8 days ago
Status changed to Solved Railway • 8 days ago