Service stuck on broken Metal builder — Railpack jobs producing no output
javierci
PROOP

25 days ago

Hey, urgent issue. Already opened a private support thread; sharing here

in case anyone hit this.

A Node.js service (production) — every deploy since switching to Railpack

lands on builder builder-goucoz and fails silently in 10–50s. Build logs

only show:

"scheduling build on Metal builder builder-goucoz"

…and nothing after.

Already verified:

  • railway.json: "builder": "RAILPACK", "metal": false
  • railpack.json present (Node 20, npm install / npm run build / node dist/index.js)
  • Dockerfile renamed so it doesn't take priority
  • 8 retries, all routed to the same broken builder
  • Railway Diagnose itself says config is correct and the issue is the builder.

Failing builder: builder-goucoz

(Service details shared privately with the Railway team via support thread.)

Has anyone seen this? Or is there a way to force-reassign builder while we

wait for support?

Thanks!

Closed

3 Replies

edgnkv
EMPLOYEE

25 days ago

I've replied to you in the private thread 15m ago.


javierci
PROOP

25 days ago

Thanks — just replied in the private thread.

This is currently blocking our deployments (all retries hitting the same builder: builder-goucoz).

Would really appreciate a manual reassignment if possible 🙏


25 days ago

Then let's stick to the previous thread. Duplicate threads split our effort to support you.


Status changed to Closed brody 25 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...