a month ago
Hey everyone,
Hoping someone has seen this before. My Python service has been failing to build for the past hour with repeated "failed to fetch snapshot" errors, and I'm out of ideas.
What's happening:
- Build gets scheduled on a Metal builder successfully
- One second later: "failed to fetch snapshot"
- That message repeats every 15-60 seconds, build stays stuck on "Building" indefinitely
- No actual build steps ever run (no pip install, no Railpack output at all)
Latest failing deployment: 974dd76e (and a04be193 before it)
I tried what the Diagnose tool suggested. It said: "Two consecutive deployments failed identically on the same builder machine, while a previous deployment with the same Railpack version and Python detection succeeded. Try redeploying to retry on a different builder."
I redeployed and got a different builder machine — same result.
My config looks clean to me:
- railway.json has builder set to RAILPACK, buildCommand removed, startCommand only in deploy phase
- A previous deployment of this exact code is still active and running fine from May 12
GitHub repo: github.com/chayshechter/trading-bot
Has anyone hit this before? Is it an infrastructure issue that resolves on its own, or is there something in my config I should change? Any help appreciated.
Thanks!
3 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Hey! this looks resolved now as I can see a newer deploy has landed.
Are you still having issues here?
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Hey @mykal - I'm having the exact same issue
Status changed to Awaiting Railway Response Railway • about 1 month ago
Hey @mykal - I'm having the exact same issue
a month ago
Could you please try redeploy or attempt a new deploy for your service and see if that helped? If not, please open a thread with us and we'll get you sorted!
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