18 days ago
Project: laudable-expression
Service: CRAFTHUB 360
Repository: coach1206/crafthub-360-stitch
Branch: recovery/smokecraft-codex-final
Latest commit: d3a63987
Title:
Metal builder repeatedly fails with “failed to fetch snapshot”
Body:
A Railway service repeatedly fails before Docker/npm starts with:
failed to fetch snapshot
I already:
- confirmed the repository and branch
- disconnected and reconnected the GitHub source
- confirmed Railway GitHub App access
- triggered fresh deployments
- fixed later application-build ENOENT issues when the build did reach npm
The service intermittently reaches the application build, then later reverts to snapshot-fetch failures on the Metal builder.
Could Railway please:
- clear the source snapshot/cache for this service
- move the service to a healthy builder
- repair the source-fetch pipeline
- trigger a clean deployment
No code, Dockerfile, image, or media changes are needed for this specific failure.
1 Replies
Status changed to Awaiting Railway Response Railway • 18 days ago
17 days ago
The snapshot fetch failures happen when you hit Redeploy on a deployment whose build already failed. A failed build doesn't leave a stored code snapshot behind, but Redeploy still points at one, so it goes looking for something that isn't there. Nothing is wrong with the builder itself, and there's no cache to clear on your side.
So push a commit instead of using Redeploy. Every deploy from a GitHub push has gone through, including your latest one, which got past the source fetch and into the build itself. Anything failing from there on will show up in that deployment's build logs.
Status changed to Awaiting User Response Railway • 17 days ago
10 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 • 10 days ago