Skip to content
Production deployment fails at Initialization → Snapshot code
Anonymous
OP

7 days ago

Hello,

I am requesting assistance diagnosing two failed production deployments that both stopped during:

Initialization → Snapshot code

Error:

“Failed to create code snapshot. Please review your last commit, or try again.”

Project: imaginative-respect

Environment: production

Service: alliyan-platform

Failed deployment IDs:

61e31d55-8e79-41a0-8859-4da08953903f

b992e10d-eeac-45c3-a3a5-dab25deef3f6

The existing production deployment remains successful:

00ddeb99-a747-4d85-9b89-2bc3c4ac3fab

We have stopped further deployment attempts while investigating.

Additional diagnostics completed:

  • Repository is clean and the target revision is pushed.
  • Local/tracking/remote revisions match.
  • Railway project/environment/service linkage is correct.
  • Current Railway CLI installation has been repaired and verified as 5.71.1.
  • Railway authentication succeeds.
  • No build or migration stage was reached during either failed deployment.
  • Earlier upload attempts experienced timeout/connection-reset behavior.
  • Current DNS/TCP/TLS connectivity checks to required endpoints succeed.

We also inspected the deployment source candidates.

Estimated current deployment candidates:

~2,548 files / ~97.91 MB uncompressed.

Tracked source at the previously successful production revision:

2,529 files / ~87.69 MB.

Current tracked source:

2,549 files / ~97.40 MB.

The increase is primarily approved image assets. The largest pre-existing source files were already present in the revision that deployed successfully.

No candidate audio recordings, databases, compressed archives, tracked symlinks/submodules, abnormal permission modes, unreadable files, or unusually long paths were identified.

Could you please inspect the two failed deployment IDs and confirm:

  1. Did Railway receive the complete source upload for either deployment?
  2. At what exact point did snapshot creation fail?
  3. Was the snapshot rejected because of source contents/size, or did an upload/source-ingestion/platform failure occur?
  4. Are there server-side logs or request IDs associated with these failures?
  5. Is another CLI deployment attempt appropriate, or is there a Railway-side issue that should be resolved first?

We do not want to alter a validated release or repeatedly retry production deployment without understanding the snapshot failure.

Thank you.

Solved

0 Replies

Status changed to Awaiting Railway Response Railway • 7 days ago


Status changed to Solved Anonymous • 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...