Deploy - failed
honzafuri
HOBBYOP

23 days ago

Build Failed: build daemon returned an error < failed to receive status: rpc error: code = NotFound desc = no such job 723d63ee-8a2e-40fe-b800-3d46417c7be8-20260430075932 >

Frontend service deploys are failing with build daemon returned an error... no such job for the past 30+ min. Same code deployed successfully earlier today. Tried multiple retries + empty commit pushes. Railway's own diagnosis says "transient infrastructure error".

9 Replies

Try disabling Metal builder.


honzafuri
HOBBYOP

22 days ago

hi. it re-enables itself every time I trigger a new deploy.


Status changed to Awaiting Railway Response Railway 22 days ago


honzafuri
HOBBYOP

22 days ago

image.png

Attachments


edgnkv
EMPLOYEE

22 days ago

cycled the builder, can you try again?


honzafuri
HOBBYOP

22 days ago

yes, it working. thank you


prochorus
PRO

22 days ago

@edgnkv, would you be able to cycle the builder for me too? Thanks!

Project ID: b8e30d2a-cfd9-4c1a-b8b0-8929dc99aeea


prochorus

@edgnkv, would you be able to cycle the builder for me too? Thanks! Project ID: `b8e30d2a-cfd9-4c1a-b8b0-8929dc99aeea`

edgnkv
EMPLOYEE

22 days ago

Can you retry the build? I've cordoned the builder, but I will look into what happened there (looks like a deadlock in buildkit).


Status changed to Awaiting User Response Railway 22 days ago


prochorus

@edgnkv, would you be able to cycle the builder for me too? Thanks! Project ID: `b8e30d2a-cfd9-4c1a-b8b0-8929dc99aeea`

edgnkv
EMPLOYEE

22 days ago

Actually, it is not a buildkit or builder issue, it is a deadlock between node and esbuild in nuxt's build orchestration (that bun runs). So build is kind of finished, but node is waiting for esbuild to report the status, and esbuild is waiting for node for a next command. Did you have this issue before? To me it looks like a bug in nuxt/esbuild.


prochorus
PRO

22 days ago

Thanks @edgnkv! I think you are right on what the issue is.


Status changed to Awaiting Railway Response Railway 22 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...