We are experiencing repeated failures during Railway code snapshot creation when deploying a Next.js production service using railway up.

The application and deployment source have been independently validated. The failure occurs after Railway accepts the upload but BEFORE Railway creates an associated build.

Railway Project

Project:

corblack-production

Project ID:

47bb6f7a-81f8-4e6c-9d22-8ae09fc34827

Service:

cor-frontend

Service ID:

84d32293-f79a-475c-8527-160ff30f7f6c

Environment:

production

Environment ID:

e363bed4-a692-4661-aff5-8322c74e095e

Railway CLI:

5.41.2

Deployment Command

The deployment command is:

railway up --project 47bb6f7a-81f8-4e6c-9d22-8ae09fc34827 --environment production --service cor-frontend

The command is executed directly from the root of the verified deployment source.

No path argument is supplied.

The current working directory is correctly resolved as the deployment/archive root.

Failure

Railway accepts the source upload and creates a deployment record, but the deployment remains in:

INITIALIZING

The affected deployments have:

• no associated build
• no build logs
• no deploy logs
• no instances
• no image digest
• no production cutover

One deployment explicitly reported:

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

and:

If this error persists, please reach out to the Railway team.

Affected Deployment IDs

7f8a0f58-3053-4959-9000-0cf0afbaca8e

d674c1f9-b36f-47b5-9921-1eda6f56bc31

8b8a2f13-34f7-4f2d-9a52-585dca9ffbc7

6a8e1ba8-3075-49c2-9986-41a1f1f3fceb

Most recent plain-source attempt:

fcc8d83f-a2c5-4dc7-8220-6774a361d05e

The most recent attempt again remained INITIALIZING with no associated build or deployment logs.

Local Source Validation

We initially investigated whether the problem was caused by deploying from a detached Git worktree.

To eliminate that possibility completely, we created a new standalone deployment source containing the exact accepted application source.

The new source has:

• NO .git file
• NO .git directory
• NO external worktree metadata
• 1,188 source files verified against the accepted artifact
• 0 missing files
• 0 extra files
• 0 hash mismatches

The same Railway snapshot failure still occurred.

Upload Payload

The complete local artifact is larger because it contains dependencies, build output, and QA/governance artifacts.

However, .railwayignore excludes:

• node_modules/
• .next/
• review-artifacts/
• verification/
• logs
• local QA evidence
• environment/credential files

The estimated effective Railway source payload is:

Approximately 124.43 MB

Included files:

692

Approximately 116.76 MB of that payload consists of legitimate public storefront image assets.

Application Validation

The application builds successfully locally.

Required root files are present:

• package.json
• package-lock.json
• next.config.mjs
• railway.json
• .railwayignore
• src/
• public/

No application/code defect has been identified that would explain a failure occurring before Railway creates a build.

Historical Context

This same Railway project/service has previously deployed successfully using the same general railway up local-source mechanism.

Examples of previous successful deployment IDs:

fc340863-8e39-47b1-8ec3-bdda04e23350

5632e96e-444d-4edb-b6ab-d607d59fb421

b51eee6a-7636-4174-85b0-d42edf3f710c

052476d6-a70b-4e97-9c01-d0093f1d04a5

Therefore local-source deployment itself has historically worked for this service.

Current Production State

We stopped additional deployment attempts.

The production website was restored successfully to the previous known-good Railway image and is currently healthy.

The issue is specifically preventing NEW source deployments from advancing past Railway's code snapshot stage.

Question

Could Railway please help determine why source uploads for this service are currently failing during code snapshot creation before any build is created?

In particular, we would like to determine whether this is:

1. a Railway snapshot/platform issue;
2. a source-upload limitation or timeout;
3. a project/service configuration issue;
4. or another issue affecting railway up snapshot generation.

We have reproduced the issue from both a Git worktree and a completely plain standalone source directory with no Git metadata, so we have stopped further deployment attempts pending guidance.