Metal builder fails immediately after scheduling — no build output
riskycards1
PROOP

2 hours ago

Could someone help identify why this deployment is failing immediately after being assigned to the Metal builder? The logs stop at scheduling build on Metal builder "builder-zdssbo" with no additional build output.

A redeploy produced the same result. I'm trying to determine whether this is a Railway builder issue or whether there is a hidden pre-build error I can fix on my side.

I'd prefer to troubleshoot the existing staging service rather than recreate or make major changes to the service, database, variables, domains, or production environment.

$20 Bounty

2 Replies

Railway
BOT

2 hours ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway about 2 hours ago


2 hours ago

Try cancel all stuck builds and Deploy Latest Commit from the Command Palette


mayori

Try cancel all stuck builds and **Deploy Latest Commit** from the **Command Palette**

riskycards1
PROOP

2 hours ago

Thanks. I confirmed there were no queued/stuck builds remaining and then triggered a completely fresh deployment from a new latest GitHub commit. It still failed immediately on builder-zdssbo with no build output after the scheduling line. New deployment ID: ec911f2c-fab8-4a43-8af9-e1eed5820c6f.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...