a month ago
Deployment ID: 109742ed-e89f-4de1-b280-d17a76c4c2b2
Service ID: a5e4c1c4-2a83-4936-9a99-b2330d6bb55c
All three latest deployment attempts fail while Railway creates a snapshot of my source code (SNAPSHOT_CODE phase):
Error: "Failed to create code snapshot. Please review your last commit, or try again."
Observations:
- Each attempt runs for exactly 15 minutes, then times out
- Build/deploy logs are completely empty
- Code is identical to successful build from August 6
- Zero file changes since last successful deployment
- Repository is accessible, main branch resolves normally
- railway.toml config unchanged
This points to an issue in Railway's snapshot infrastructure, not in the code.
2 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your code isn't the problem. Those deploys failed because the CLI's upload of your source archive stalled partway through, so Railway sat waiting on an incomplete stream and gave up at the 15 minute mark. That's why the build logs are empty, the build never started.
Worth knowing: the successful August 6 deploy came from GitHub, not the CLI, so it took a different path than today's attempts. The service is still connected to neikoon/story-lab-digital, so a push to that repo deploys without going through the CLI upload at all.
Five upload attempts overlapped this morning, all competing for the same connection, which makes a stall more likely. One attempt at a time has a better chance of getting through. The deployment left hanging at the snapshot step has been cleared, so a retry starts clean.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
Thank you!
Status changed to Awaiting Railway Response Railway • about 1 month ago
Status changed to Solved neikoon • about 1 month ago