a month ago
Hi team,
The build system has been unable to start builds for this service across
4 consecutive deployments. Each time the snapshot completes successfully
but the build process never launches — producing zero/empty build logs.
Confirmed via Railway's own auto-diagnose:
"Infrastructure Error — The build system has been unable to start builds
for this service across four consecutive deployments. Each time, the
snapshot completes successfully but the build process never launches,
producing zero build logs."
The original TypeScript error from the first failure was fixed in commit
3491f16. Code is valid — tsc --noEmit passes locally. The most recent
deploy (commit 2de064d) is an empty commit specifically to rule out code
issues, and it failed identically.
Steps already attempted:
- Multiple redeploys
- Empty commit to force fresh snapshot context
- Verified billing is active and quota not exceeded
Project ID: Jarvis-bonfim
Service ID:
Latest Deployment:
Commit on main: 2de064d (empty commit)
Repo: github.com/bwdenis/jarvis-bonfim
Could you please force-reset the build runners assigned to this service,
or investigate why BUILD_IMAGE is silently failing for this service
specifically? Other services in the same project (if any) are unaffected.
Thanks.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
This is an infrastructure-side issue currently affecting build log delivery and some build processes. You can follow updates at the active incident here: https://status.railway.com/incident/M0XS8E8V. Please cancel any queued builds to avoid compounding the queue, and retry once the incident is resolved on our end.
Status changed to Awaiting User Response Railway • about 1 month ago
23 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 • 23 days ago