Hello Railway Support,

We're experiencing repeated failures deploying an update to our BridgeSpace staging application through the Railway CLI.

The application is currently running successfully on Railway, and our existing deployment remains healthy. However, two consecutive attempts to deploy a small, tested code change have failed before the build process begins.

Project: BridgeSpace

Environment: production (our established staging environment)

Service: bridgespace-staging

Service ID: 45ed61a4-7cab-44f2-a6f1-987f259930dc

Railway CLI version: 5.64.2

Source commit: 65f287169b3da98d05f8a625f4107c8ea9fc1ec2

Failed deployment IDs:

• 72f7c5ef-d563-468b-8ea3-02f5ab47be37
• 533aae95-b144-424a-a7e7-4c8141d23525

Both attempts completed local indexing and compression but timed out while uploading the archive to Railway's /up endpoint.

Railway subsequently marked the deployments as FAILED with the message:

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

No build logs were generated, and the application never reached the build or startup stage.

We've verified that:

• The source checkout is clean.
• TypeScript checks, 83 focused tests, and the production build pass locally.
• Railway authentication works.
• The correct application service was explicitly selected.
• The MySQL service was not targeted.
• The existing successful deployment, 6103f31f-f292-4df7-a395-76f59eafd4aa, remains active and healthy.
• The staging database is accessible.

We previously encountered a similar code-snapshot failure with this project, which was resolved after a later controlled CLI deployment attempt.

Could you please investigate why code snapshot creation is failing and advise whether there is a known issue with the CLI upload endpoint or an alternative supported deployment method?

We would prefer to preserve our current CLI-based deployment workflow rather than change repository connections or production configuration.

Thank you for your assistance.