24 days ago
My deploys are failing at the Build → Build image step in about 6 seconds. The Build Logs only show:
activity ScheduleToStart timeout
This looks like a Railway-side build scheduling issue, not my code. My last change didn't touch the Dockerfile, railway.json, or any dependency files — the build inputs are identical to the last successful deploy, and railway.json correctly specifies the Dockerfile builder. A real build takes several minutes, so a 6-second failure means the build never actually started — the job was queued but no build worker picked it up.
I've already redeployed several times with the same result. Could you check whether there's a build-queue capacity or scheduling problem on your side? Thanks.
1 Replies
24 days ago
Your build failures are caused by an ongoing incident affecting our build infrastructure. To reduce a backlog of queued builds, we have temporarily paused new builds on free, trial, and hobby plans. This is why your build never starts and times out after a few seconds. You can follow progress at this incident page, and your builds should succeed once we've cleared the queue and resumed normal operations.
Status changed to Awaiting User Response Railway • 24 days ago
17 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 • 17 days ago