Hello, I'm experiencing a persistent build infrastructure issue with the queue-worker service in my production environment. The build is failing consistently with an RPC "NotFound" error, and multiple redeploys have not resolved the issue. **Details:** * **Environment:** production * **Service:** queue-worker * **Branch:** main * **Failed Deployment IDs:** * 1b564131-0381-4d15-812b-387d921666b4 (2026-05-14T14:31:48Z) * 7f46cb52-5352-4b4c-8780-7eea89da7db9 (2026-05-14T13:08:01Z) * af924204-d054-4c7c-be29-e9b4bafd9278 (2026-05-14T12:49:40Z) **Error Message:** ``` Build Failed: build daemon returned an error ``` **Timeline:** * Last successful build: 2026-05-14 at 03:20 UTC * Failures started: \~2026-05-14 at 11:39 UTC * Affected: All main branch deployments since then (7+ failures) **Key Observations:** * The develop branch builds successfully on the same service with the same Dockerfile * The triggering commit only adds release notes (no build-relevant changes) * The issue appears to be infrastructure-related, not code-related * Multiple redeploy attempts have not resolved the issue Could you please investigate this build daemon issue? Any assistance would be greatly appreciated. Thank you, Leandro

Build Infrastructure Error - queue-worker Service Failing on Main Branch

leandrogrando

PROOP

8 days ago

Hello,

I'm experiencing a persistent build infrastructure issue with the queue-worker service in my production environment. The build is failing consistently with an RPC "NotFound" error, and multiple redeploys have not resolved the issue.

Details:

Environment: production
Service: queue-worker
Branch: main
Failed Deployment IDs:
- 1b564131-0381-4d15-812b-387d921666b4 (2026-05-14T14:31:48Z)
- 7f46cb52-5352-4b4c-8780-7eea89da7db9 (2026-05-14T13:08:01Z)
- af924204-d054-4c7c-be29-e9b4bafd9278 (2026-05-14T12:49:40Z)

Error Message:

Build Failed: build daemon returned an error < failed to receive status: rpc error: code = NotFound desc = no such job >

Timeline:

Last successful build: 2026-05-14 at 03:20 UTC
Failures started: ~2026-05-14 at 11:39 UTC
Affected: All main branch deployments since then (7+ failures)

Key Observations:

The develop branch builds successfully on the same service with the same Dockerfile
The triggering commit only adds release notes (no build-relevant changes)
The issue appears to be infrastructure-related, not code-related
Multiple redeploy attempts have not resolved the issue

Could you please investigate this build daemon issue? Any assistance would be greatly appreciated.

Thank you, Leandro

Solved

3 Replies

Status changed to Awaiting Railway Response Railway • 8 days ago

sam-a

EMPLOYEE

8 days ago

Your diagnosis was correct, this was infrastructure related and not your code. We've mitigated it. Please trigger a fresh deploy of queue-worker and it should go through.

Status changed to Awaiting User Response Railway • 8 days ago

douglas125

PRO

8 days ago

Same.

Details:

Three consecutive deployments for the worker service failed with the same build infrastructure error:

Build Failed: build daemon returned an error < failed to receive status: rpc error: code = NotFound desc = no such job ... >

Deployment IDs:

d594b228
1d0137c2
fca9067c

Timeline: Failures occurred between 14:09 and 15:35 UTC (roughly 1.5 hours apart)

Builder: All three deployments were scheduled on builder-wkkdbn

Status changed to Awaiting Railway Response Railway • 8 days ago

Status changed to Solved leandrogrando • 8 days ago

sam-a

Your diagnosis was correct, this was infrastructure related and not your code. We've mitigated it. Please trigger a fresh deploy of queue-worker and it should go through.

leandrogrando

PROOP

8 days ago

It's working now. Thank you!

Status changed to Awaiting Railway Response Railway • 8 days ago

Status changed to Solved Railway • 8 days ago

Welcome!