Failed to snapshot repository — platform-side error confirmed by Railway diagnostic
Anonymous
FREEOP

7 days ago

Every deploy fails at Initialization › Snapshot code in 4 seconds with "Failed to snapshot repository."

Railway's own diagnostic tool confirms: "This deployment failed during the source snapshot step due to a platform-side error, before any build or deploy steps could run. The same failure occurred on two prior attempts within minutes, with no build or deploy logs produced."

Project ID: 335530af-5984-44b1-911c-16d182890769

Service ID: 5de6a863-472e-4049-9b38-0eaea3b9d6a9

Deployment ID: e1abe562-37fa-41d0-9a93-ee841135e3ac

Local repo is clean (47 files, 160KB). Git initialized. No large files. Issue persists across multiple service IDs and multiple CLI attempts. Please reset the snapshot backend for this service.

Awaiting User Response

1 Replies

Status changed to Awaiting Railway Response Railway • 7 days ago


sam-a
EMPLOYEE

7 days ago

Your latest deployment got past snapshotting and built successfully. The earlier attempt failed while parsing railway.json; our diagnostic incorrectly described that as a platform error, sorry for the confusion.

The bot now crashes at startup with DiscordjsError [TokenInvalid]. Check that the production service has the environment variable your code passes to client.login() populated with your Discord bot token, then redeploy.


Status changed to Awaiting User Response Railway • 7 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...