Skip to content
GCRS-ADHESION deployment fails at Code snapshot before build
Anonymous
OP

2 months ago

Hello,

Two consecutive deployments of my GCRS-ADHESION service in production failed at the “Code snapshot” stage, before the build started.

I deploy from Windows using the Railway CLI:

npx.cmd @railway/cli up --service GCRS-ADHESION

The CLI finishes compressing the files, then reports “error sending request” and “operation timed out”.

The Railway dashboard reports “Failed to create code snapshot”. Its diagnostic tool says the cause is not visible in the available logs.

Affected deployment: 813b1f3d

Date: October 2, 2026, at 11:21 AM UTC+2.

The previous deployment is still online. Could you investigate what is blocking the code snapshot creation?

Thank you.

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • about 2 months ago


a month ago

Both attempts stopped while the code snapshot was being created, before any build began. No new container was started, so your current deployment was not replaced by either attempt.

Please run railway up --service GCRS-ADHESION again. The snapshot step can be retried safely, and your running deployment stays online if it fails again.


Status changed to Awaiting User Response Railway • about 2 months ago


a month ago

Both uploads from the CLI stopped before they finished. On each attempt the connection carrying your files closed after about 90 seconds, which is the CLI's request timeout, so the snapshot was never created and no build started.

railway up uploads everything in the directory except what .gitignore and .railwayignore exclude, plus .git and node_modules (CLI docs).


Railway
BOT

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 • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...