Skip to content
Two consecutive CLI deployments fail during build and repository snapshot (US West, Hobby)
Anonymous
OP

a month ago

Hello Railway team,

I'm using the Hobby plan and experiencing repeated deployment failures on my US West service.

Two consecutive CLI deployments of the same application source failed at different stages:

Attempt 1 – Build Image Failed

Railpack version: 0.43.0

Error: frontend grpc server closed unexpectedly

Failed before application startup.

Attempt 2 – Initialization Failed

Error: Failed to snapshot repository. Please try again in a few minutes.

Source indexing, compression, and upload completed successfully.

Build and deployment never started.

Failed deployment ID: 5c164f34-eaca-44a1-851c-a11193501f9f

Environment

Plan: Hobby

Region: US West

Application: Python

Deployment method: Railway CLI (railway up)

Existing deployment remains active and healthy.

The application passed local syntax, integrity, and automated tests.

Could you please help determine whether this is related to an ongoing snapshot/build infrastructure issue, and suggest a safe workaround or when to retry?

I would prefer to avoid unnecessary repeated builds.

Thank you!

Solved

1 Reply

Railway
BOT

a month ago

Neither failure came from your application code. Your second attempt failed while we were creating the code snapshot, after about three and a half minutes, so the build never started. Your first attempt failed in the image build step before any of your own build commands ran.

We had build pauses on October 20 and early on October 21, but both had ended before these attempts, so they do not explain these failures. Your current deployment is unaffected, and one fresh railway up is a reasonable next step. If the snapshot step fails again, keep the upload small: add a .railwayignore that excludes local caches, virtual environments, logs and generated files, because the full project archive has to upload in under 125 seconds.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

21 days 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 • 21 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...