a month ago
Hi Railway team,
Our production service has had multiple deployments fail with an identical symptom across two separate days, with completely different code changes each time — this points to an infrastructure issue on the builder side rather than anything in our repo.
Project: extraordinary-trust (cf6dc542-275d-4b93-bac7-72f8bf7fb3c4)
Service: evtiq (e2eff393-2429-481b-9f34-d0a9c70a5145)
Environment: production (2ecd034b-5419-4717-b740-9a4033309bdd)
Region: sfo
Symptom: railway logs --build shows only:
scheduling build on Metal builder "builder-vmpxkv"
and never progresses — no compile output, no error, nothing further. The deployment is then marked FAILED after a short timeout. This happens even though npm run build of the exact same commit completes successfully locally in under 20 seconds.
Failed deployments (all with this exact symptom):
2026-07-17 22:22:19 — e4af4ef7-588e-4c17-90d8-d54e894bc7ff
2026-07-17 22:34:39 — a3067e0e-9a3d-465e-b94a-01846e758272
2026-07-17 22:37:01 — 7e5c17e8-536e-4bae-951f-c3db3a1ba89e
2026-07-17 22:39:19 — c778863d-6c85-4384-b973-3456e99f1330
2026-07-19 16:46:31 — 67f218ab-0695-4e87-8e40-7c87ad7df39b
Last successful deployment for comparison:
2026-07-17 20:07:21 — 4c9af40a-04c4-4d21-852d-6f0675b015e7 (built and started fine, served traffic, but was still flagged "Deploy failed" in the dashboard/CLI status despite a SUCCESS build — a second, separate inconsistency we noticed)
We've tried:
railway redeploy (re-ran the same already-failed build, no new attempt)
railway redeploy --from-source (created a new deployment, same "stuck at scheduling" result)
Pushing a fresh commit via GitHub (same result)
The production app is currently still online and serving traffic (Railway kept the last successful container running), so there's no outage, but we've been unable to ship several pending updates for 2 days now.
Could you check the Metal builder pool ("builder-vmpxkv") for our project, and let us know if there's a queue/capacity issue or something else blocking builds from starting?
Thanks!
3 Replies
a month ago
Your workspace's Hobby subscription is currently not active, and there is no payment method or billing history on file. You can reactivate by heading to your workspace billing settings and subscribing to the Hobby plan. Once the subscription is active, try deploying again and let us know if builds are still stuck.
Status changed to Awaiting User Response Railway • about 1 month ago
Railway
Your workspace's Hobby subscription is currently not active, and there is no payment method or billing history on file. You can reactivate by heading to [your workspace billing settings](https://railway.com/account/billing) and subscribing to the Hobby plan. Once the subscription is active, try deploying again and let us know if builds are still stuck.
a month ago
Update: I added a payment method and the Hobby plan shows as active in billing (a small charge already went through). However, builds are still stuck at the exact same point — I've retried 3 times since adding the card (including waiting ~1 minute between attempts in case it needed to propagate), and every attempt produces the identical log:
scheduling build on Metal builder "builder-gkakdh"
with nothing after that, no compile output, no error. Deployment IDs from these post-billing attempts:
6d5636fa-36b4-4e15-a679-3bf44b8c288f
0841447e-81d4-452c-b179-6054cbc58c30
4fd6cee3-40c7-47d6-ac50-9367d5502f8c
Can you confirm on your end whether billing activation has actually propagated to the build scheduler for this project, or if something else is still blocking it?
Update (next day): I also completed the plan "update" step in billing settings (not just adding the card), and retried again — deployment be1f9fb1-04c9-4d60-8aca-a93bb7646a05, over 24 hours after adding the card, same exact "scheduling build on Metal builder" with nothing further. This is now 5 identical failures after every billing-side action we could find. We still have plenty of the included $5/month usage unused, so this doesn't look like a credit/quota exhaustion issue either. Could someone manually check the build queue/scheduler for project cf6dc542-275d-4b93-bac7-72f8bf7fb3c4?
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your Hobby subscription is confirmed active (paid July 20). The builds are being blocked by a multi-region configuration on this service - one of your recent deployments explicitly failed with "Your plan can only deploy to a single region." The Hobby plan only supports deploying to one region. If you have a railway.toml or railway.json in your repo with a multiRegionConfig section, that will override the dashboard setting and block every deploy. Remove any multi-region config from your config-as-code file, ensure only one region is selected in your service's settings (under the Scale section), and redeploy.
Status changed to Awaiting User Response Railway • about 1 month ago
25 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 • 25 days ago