We are experiencing a reproducible Railway staging deployment failure that appears to occur in Railway's deployment/activation layer.

The application build completes successfully and the Docker image exports/pushes successfully. Railway then marks the deployment FAILED before the application runtime starts. No application/deploy runtime logs are produced.

Troubleshooting already completed:

• Reproduced on the original staging service.

• Created a separate clean-room staging service and reproduced the same failure.

• Created a fresh Git commit/snapshot rather than only redeploying an existing deployment; failure persisted.

• Confirmed the intended independent GitHub branch is being used.

• Docker build/image creation completes before the failure.

• No runtime/deploy logs appear after the image is built.

• Existing application safety/authentication configuration has not been weakened to work around the failure.

This reproduction across two independent services makes a single corrupted service or ordinary application-runtime failure unlikely.

Please investigate the project/environment deployment activation or provisioning layer and advise whether there is a project-level, environment-level, builder, scheduler, or deployment infrastructure issue.

Note: the workspace has now reached its separate Railway Agent usage limit ($5), but infrastructure/compute usage has not reached a hard limit. These deployment failures were occurring independently of the Agent limit.

We can provide specific deployment IDs, project/environment IDs, timestamps, and additional build evidence if required.The attached service is the original failing staging service; the same failure was independently reproduced on nurse-brain-cleanroom-staging, providing a second-service reproduction.