8 days ago
[Resolved] Build daemon "no such job" RPC error on builder-wkkdbn — affected multiple Pro/Hobby accounts; mitigated by Railway. See sibling thread: https://station.railway.com/questions/build-daemon-no-such-job-rpc-error-4-696a38b1
3 Replies
Status changed to Awaiting Railway Response Railway • 8 days ago
8 days ago
(edited) Diagnostic details removed — see sibling thread for the canonical version: https://station.railway.com/questions/build-daemon-no-such-job-rpc-error-4-696a38b1
8 days ago
Confirming the same failure on a different project — builder-wkkdbn is wedged across tenants, not service-specific.
- Service:
noli-erp· Project:easygoing-transformation· Environment: production - 11 consecutive failures since ~06:05 PT 2026-05-14, identical error:
build daemon returned an error < failed to receive status: rpc error: code = NotFound desc = no such job <deploy-id>-<timestamp> > - Dies at
snapshot-target-unpack/uploading snapshot— BuildKit never invoked, exactly as you described. - Ruled out code/config the same ways you did: last successful deploy contains all current code; fresh commit (new snapshot hash) fails;
railway upCLI fails; isolated single deploys fail. - Failed deployment IDs:
546adbca, 92983e2d, bb991bdb, 263c9c9c, 8f9fd624, 3e8215a9, 94617c60, fce7013e, 0596f7c8, 5a06b879
Same ask: route both services off builder-wkkdbn, or restart the node.
6 days ago
Resolved per sam-a's mitigation in the sibling thread (https://station.railway.com/questions/build-daemon-no-such-job-rpc-error-4-696a38b1) — a fresh redeploy now goes through cleanly. Thanks!
Status changed to Solved yarinco1 • 6 days ago