8 hours ago
My deployment has been failing repeatedly with "failed to fetch snapshot" errors for over
an hour now, across multiple builder machines (builder-rmethc, builder-giheta,
builder-aahlhs). I've tried redeploying multiple times with no success.
This looks like the same issue reported here (marked Solved, but I can't reply since it's
closed): https://station.railway.com/questions/builds-stuck-on-failed-to-fetch-snapsho-d496ddc1)
Railway's own deployment failure diagnostic confirmed: "This deployment failed because
Railway's builder repeatedly could not fetch the code snapshot needed to start the build,
even after retrying on three separate builder machines over more than an hour. This was
not caused by your code or configuration."
I've independently verified on my end:
- Root Directory is correctly set to /game-barrage/backend
- No syntax errors in any backend files
- package.json is valid
- The last successfully deployed commit built fine minutes before this started
Service: incredible-forgiveness
Region: US East
Could someone please take a look? Thanks!
2 Replies
Status changed to Awaiting Railway Response Railway • about 8 hours ago
7 hours ago
This is quite urgent for me — I'm actively building a live-streaming interactive app and
this is currently blocking all my progress. I'd really appreciate any help getting this
unstuck as soon as possible. Thank you so much!
an hour ago
Your builds are already working again. The deployment from your 23:13 UTC push built fine, and the latest one is live.
The stuck attempts were all redeploys of one deployment whose first build failed a few seconds in, before Railway had saved its code snapshot. Redeploy still pointed at that missing snapshot, so every builder that picked it up failed the same way. Nothing was wrong with your code, your root directory, or the builders.
Going forward, push a commit or redeploy a deployment that previously succeeded. Redeploying one that failed at the very start of its build will loop like this.
Status changed to Awaiting User Response Railway • about 1 hour ago