21 days ago
I'm unable to deploy the api service via railway up CLI. All builds get stuck on the Metal builder "builder-zzixyx" and fail without any build logs.
Project & Service
Project: giving-spontaneity (e1c662f3-c133-4c18-ad96-5ae80c1d1dbc)
Environment: production (4c4140bd-484d-4581-a37a-ae09f79e1302)
Service: api (32a33af6-a1ed-4784-b456-855b70186588)
URL: https://approc-api.up.railway.appWhat I'm trying to do Deploy via railway up from repo root with:
Builder: Dockerfile
Dockerfile Path: apps/api/DockerfileExact symptoms
CLI uploads correctly ("Uploaded")
Build starts, SNAPSHOT_CODE completes (~5 sec)
BUILD_IMAGE fails immediately after
Build logs only show: scheduling build on Metal builder "builder-zzixyx" (repeated 2x)
No actual build steps ever appear (no npm ci, COPY, etc)
Total time to fail: ~5 seconds with zero builder outputFailed deployments (all identical failure pattern)
19483d4a-da5c-4d21-818a-e1ed9d113b28 (09:15 UTC)
2a105f1a-317c-4fdb-aa77-db33b17f5e28 (09:20 UTC)
fffdd4ad-d480-4270-b14f-afc188c0a567 (09:25 UTC)Reproducibility 4-5 attempts over ~20 minutes today, all stuck identically on builder-zzixyx. Same issue observed in previous sessions.
Important observation A manual redeploy from the dashboard succeeded at some point — so the build system is not totally down, only this specific CLI path / queue is blocked.
Questions for support
Is builder-zzixyx down, saturated, or experiencing an outage?
Is there a known issue with railway up and this builder queue?
Can you check the infrastructure logs for builder-zzixyx and these three deployment attempts?1 Replies
21 days ago
The build logs for these deployments show no changes detected in watch paths, build will skip before the build fails. Your service's watch path is set to apps/api/Dockerfile only, so when railway up uploads code and the Dockerfile itself hasn't changed, the build system sees no relevant diff and skips the build entirely. Broadening the watch path to /apps/api/** will let CLI deploys detect your actual source changes and build normally.
Status changed to Awaiting User Response Railway • 21 days ago
14 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 • 14 days ago