a month ago
Hi,
My Railway deployments are repeatedly failing during code-snapshot creation.
- Project: 274a8eaf…
- Environment: b0b41abb…
- Service: d12714f2…
- Railway CLI: 5.48.0
- Deployment method: local CLI upload using railway up --service <SERVICE_ID> --detach
The CLI stalls at “Taking a snapshot of the code” and eventually reports:
error sending request for url:
https://backboard.railway.com/project/<PROJECT_ID>/environment/<ENVIRONMENT_ID>/up?serviceId=<SERVICE_ID>
Caused by:
operation timed out
Railway subsequently records:
Failed to create code snapshot. Please review your last commit, or try again.
If this error persists, please reach out to the Railway team.
Example affected deployments:
- 69aa9b48…
- 3091deed…
- cb37bd83…
- 55f48ae4…
- ecfeef83…
The issue is intermittent but recurring. One deployment succeeded on 2 September at approximately 05:51 UTC, while snapshot attempts immediately before and after it failed.
Checks completed:
- CLI authentication is valid.
- The service has source: null and uses a local CLI upload, not a linked GitHub repository.
- Watch Paths are empty: watchPatterns: [].
- The prepared production payload is approximately 26.35 MiB across 1,485 files.
- The production tree contains no symlinks.
- .git, node_modules, logs, admin files and database backups are excluded.
- No unexpectedly large or recently generated files were found.
- The failures occur before a build is created, so there are no relevant build logs.
- The Railway status page reports the platform as operational.
Any ideas on what else might cause the uploaded archive to repeatedly fail during code-snapshot creation? Thanks everyone
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
Your setup isn't the cause here. 26 MiB across 1,485 files is small, the empty watch paths and null source are both correct for a CLI upload, and nothing in the checks you ran was a wrong turn. There's no configuration change on your side that would fix this.
What's happening is that the upload times out before the snapshot gets created. There are two different places that can happen, one in the CLI itself and one further in on our side. They look identical from where you're sitting, but they have different causes and different fixes, so we'd rather not guess at which one you're hitting.
One thing would tell us: roughly how long does it take from running railway up to the error appearing? Thirty seconds and fifteen minutes point at opposite halves of this.
Your deployment at 19:12 UTC on 2 September did succeed and is the one currently running, so this is intermittent rather than a hard block while we sort out which half it is.
Status changed to Awaiting User Response Railway • about 1 month ago
a month 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 • 26 days ago