Build stuck/failing for 19 hours - Metal builder accepts job but produces no output (US West)
automatizacionesvenetianblinds
HOBBYOP

a month ago

Hi Railway team,

A build on a Hobby plan project has been failing for approximately 19 hours.

Project: robust-commitment

Service: venetians_samples

Region: US West

Plan: Hobby

For the past 19 hours, every redeploy of commit 75d91cf either fails or hangs on "Building the image". Previous deploys on the same setup (commit 0f8525f) succeeded cleanly. I have not changed package.json, the Dockerfile or any build configuration since.

Build Logs of a failed attempt (deploy 83e620aa, June 2 at 12:20 PM GMT+2) show only one line:

scheduling build on Metal builder "builder-xojpoe"

After that, nothing. No dependency install, no compile step, no error output. The auto-diagnosis says "Infrastructure Error - scheduled on Metal builder but failed without producing any output".

I have redeployed multiple times over the last 19 hours. The same pattern repeats: some fail at around 16 seconds, others hang in "Building the image" indefinitely. The dashboard banner has also been showing "Dashboard Logs Loading Slowly. We have pushed a fix and are monitoring the incident" throughout, which seems possibly related.

Could you please check the Metal builder pool for this service and region? I am happy to share more deployment IDs if useful.

Thank you.

Solved

1 Replies

Railway
BOT

a month ago

We're aware of these transient build queue issues and are actively working on improvements. In the meantime, we'd recommend cancelling any queued or hanging builds rather than redeploying repeatedly, as additional deploys can compound the queue pressure.


Status changed to Awaiting User Response Railway about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway 27 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...