Deployment stuck at code snapshot stage — repeated timeouts
keithmn
FREEOP

22 days ago

My deployment (ID: e1a88a50-d17b-4185-b3b4-b23909581732) failed while Railway was creating a code snapshot, before any build or start steps ran.

The failure details:

Failed at SNAPSHOT_CODE stage with timeout after ~15 minutes

Build and deploy logs are empty (failure happened before build could start)

Four consecutive deployments failed identically at SNAPSHOT_CODE with the same timeout

A deployment just before this streak completed successfully through all stages (snapshot, build, container creation, network config)

Newer deployments queued after are also stuck pending at SNAPSHOT_CODE

No repo/branch/commit metadata available for the failed deployment

This appears to be a systemic issue in the snapshot pipeline rather than anything in my code or service configuration. The source code itself is not the problem, as a deployment immediately prior to this streak completed successfully.

Service ID: b27c5016-1a91-4914-9d9e-c78c8cdeee20 Environment: production (051232e0-cf33-4f31-a5af-bd7d641b3288) Project: sportscast (0734d88f-7ce5-44f8-9e43-d5266816f6f9)

$10 Bounty

1 Replies

Railway
BOT

22 days ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway • 22 days ago


22 days ago

does this happen when deploying from a github commit or using railway up?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...