14 days ago
Hi Railway Support,
We have a Railway Metal builder instance that has become unhealthy and appears to be permanently pinned to our jumiaintel service. All deployments are now failing.
Account: contact@haemetcapital.com
Project: angelic-victory
Service: jumiaintel
Service ID: bb126cba-1be4-471d-b283-eae8c439d48d
Environment ID: c3af0ff5-464f-49a5-abaa-6af269513fdb
Symptoms:
- Deployments fail with build log showing only 1 line: [info] scheduling build on Metal builder "builder-msoxio"
- Build goes INITIALIZING -> BUILDING -> FAILED (sometimes INITIALIZING -> FAILED with no build output at all)
- A no-op commit to force builder rotation also fails (same builder assigned)
- Railway status page shows 100% uptime -- this appears to be an isolated builder instance failure
We believe "builder-msoxio" is unhealthy and has been pinned to our service since around 19 Sep 2026. This is blocking all our deployments.
Please could you detach builder-msoxio from our jumiaintel service and assign a healthy builder instance?
Note: We sent an earlier support request about this from a different email (dtsourceandship@gmail.com) but Railway support replied that they could not match the request to our account. This ticket is submitted from contact@haemetcapital.com which is the registered account owner.
Thank you,
Daniel (Haemetcapital)
6 Replies
14 days ago
Your most recent deployment on the jumiaintel service in angelic-victory completed successfully today at 05:29 UTC, built on builder-msoxio with a full build pipeline (Vite + esbuild completed, image exported and pushed). The service is currently in a healthy SUCCESS state with no deployments queued or stuck.
14 days ago
This thread has been marked as private.
Status changed to Awaiting User Response Railway • 14 days ago
14 days ago
Thank you for the response, but this does not match our experience today. The successful deployment referenced (05:29 UTC, deployment 4f41b5e0) was for commit ff2c97d0 (OPP-004). That worked fine.
Two subsequent deployments today FAILED with zero build log output — only the single line [info] scheduling build on Metal builder "builder-msoxio" and no build pipeline output at all:
Deployment c5cd504f — triggered 12:43 UTC 22/09/2026 — FAILED
Deployment 7545a4e8 — commit c7470b58 — triggered 12:53 UTC 22/09/2026 — FAILED
The builder worked at 05:29, then became unhealthy again. Every deployment since has produced zero build log output and fails. We cannot deploy our service at all.
Could you please escalate this to a human engineer to investigate what happened to builder-msoxio between 05:29 and 12:43 UTC today?
Status changed to Awaiting Railway Response Railway • 14 days ago
14 days ago
Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.
This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.
Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.
- Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
- Keep it private and close the thread - Nothing becomes public and the thread closes.
Status changed to Awaiting User Response Railway • 14 days ago
14 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 14 days ago
14 days ago
Thank you for the response, but this does not match our experience today. The successful deployment referenced (05:29 UTC, deployment 4f41b5e0) was for commit ff2c97d0 (OPP-004). That worked fine.
Two subsequent deployments today FAILED with zero build log output — only the single line [info] scheduling build on Metal builder "builder-msoxio" and no build pipeline output at all:
Deployment c5cd504f — triggered 12:43 UTC 22/09/2026 — FAILED
Deployment 7545a4e8 — commit c7470b58 — triggered 12:53 UTC 22/09/2026 — FAILED
The builder worked at 05:29, then became unhealthy again. Every deployment since has produced zero build log output and fails. We cannot deploy our service at all.
Could you please escalate this to a human engineer to investigate what happened to builder-msoxio between 05:29 and 12:43 UTC today?
14 days ago
Your logs show esbuild failures. Unfortunately, we can't support application-level issues, so the community remains the correct path forward for support.
Status changed to Awaiting User Response Railway • 14 days ago
14 days ago
Deployments fail with build log showing only 1 line: [info] scheduling build on Metal builder "builder-msoxio"
Although I would like to know where you are seeing only one line, I can see a full multiline error that shows the esbuild error.
7 days 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 • 7 days ago