18 days ago
I use railway via claude and for about month everything was good, i had massages like build failed every time claude deployed build via cli but the real deploy was sucess. But today something gone wrong and real deploys fails, only one from 20 failed deploys was ok today ut i didnt find the reason why
Deployment failed during the initialization process
View less
Initialization › Snapshot code
(15:00)
Failed to create code snapshot. Please review your last commit, or try again.
Diagnosis › Try running a diagnosis to understand why this deployment failed.
Diagnose
Build
Not started
Deploy
Not started
Post-deploy
Not started
2 Replies
18 days ago
upd build is finally goes ok but i cant understand what is the main problem if even logs not working correctly
18 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 18 days ago
18 days ago
asked claude to add some notes:
Deploy method: railway up --detach (CLI source upload, not GitHub), CLI v5.15.0, upload ~36 MB, from macOS.
For ~1 month: CLI printed Failed to upload code with status code 500 / operation timed out, but the deploy actually completed server-side — the CLI error was cosmetic (failed on response-receipt, not on the deploy itself).
Today it changed: same CLI errors, plus real failures at Initialization › Snapshot code → Failed to create code snapshot.
Notable signal: intermittently the CLI dies with a TLS error cannot decrypt peer's message on the upload connection — looks like an unstable upload transport, not the commit.
Hit rate today ~1 success / 20 attempts; only fix is retrying railway up until a Build Logs: URL is returned.
Hypothesis for staff to check: is the snapshot step failing because the uploaded archive arrives incomplete/corrupt due to the flaky upload connection? The diagnosis blames "your last commit", but the same commit succeeds on retry with no changes — which points to the upload path, not the code.