Builds failing with no output on Metal builder — 3 consecutive failures
stsebas2
PROOP

21 days ago

Hi team,

Since 16:03 CEST today (2026-05-23) all builds on my projects are failing

with no output. Build logs only show "scheduling build on Metal builder ..."

and then nothing for 5 min until timeout.

Affected projects:

  • reserva-hamacas-production (services: reserva-de-hamacas, zesty-eagerness)
  • reserva-hamacas-staging (services: backend-staging, frontend-staging)

Failed deployment IDs:

  • 05d5330d-fda7-4287-8d01-4be088e2c402 (backend prod, 16:03)
  • 95de975e-d5e6-4639-9a3b-f53cb1865b72 (backend prod, 16:08)
  • 245a5e8f-9d2d-4958-956b-ee89b1bfc5df (backend prod, 16:12)

Last successful deploy at 14:24 same day. Same builder ID

"builder-exhnba" assigned across failures. Triple empty-commit retry

didn't help.

My account usage is normal ($10/$20 included Pro plan, plenty of headroom),

so this looks like a Metal builder infrastructure issue on your side.

This matches the same pattern as recent resolved threads:

  • "Builds repeatedly failing on builder-wkkdbn with no such job error" (9 days ago, marked [Resolved] — mitigated by Railway)
  • "Metal builder europe-west4-lk9b hardware degradation" (1 month ago, Solved)
  • "Deployment failing without any code changes" (1 month ago, Solved — Brody@Railway acknowledged builder scheduling issue)

My builds are all routed to "builder-exhnba" consistently across 3 retry attempts, suggesting builder affinity rather than random reassignment. Could you reassign my services to a different builder or restart builder-exhnba?

Could you investigate? Production deploys are currently blocked.

Thanks!

Solved

1 Replies

Status changed to Awaiting Railway Response Railway 21 days ago


19 days ago

Hey, sorry for the delayed response here.

Just took a look at your services, and I can see you had builds as recently as 40 minutes ago. Guessing that means everything got resolved here?

Let me know if there's anything else I can help with. Have a great day.


Status changed to Awaiting User Response Railway 19 days ago


Status changed to Solved mykal 19 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...