2 months ago
We are unable to deploy a verified Flask application because every attempt stops at SNAPSHOT_CODE before any build begins.
Affected deployment IDs:
- Production: f7385fc5-4ce2-4cde-ba58-50f09150fa2b
- Production: dca65a20-f2e0-48c0-ba2e-94aca1b508d6
- Isolated staging: a71e5f34-3cbb-4fbb-b4a4-a4d462ec7cc6
- Isolated staging: 0c75e72c-43cc-48c3-98c7-abe00e89fb2b
Railway displays: "Failed to create code snapshot. Please review your last commit, or try again."
For each attempt, deployment stops in SNAPSHOT_CODE before the build; snapshotId is null; there is no build association, runtime instance, or build log. A retry in isolated staging failed identically.
The upload payload has been independently checked: 684 regular files, 90,918,969 bytes, canonical SHA-256 fingerprint 197fd1cf71e07c02ca64285dce0a1ae7ac3e5f2406e01076bf3724be082245d8. It contains no symlinks, special files, AppleDouble files, .DS_Store files, or long paths; every manifest hash matches.
Could you diagnose why Railway cannot create the code snapshot and confirm whether a missing Git commit/provenance requirement is triggering this failure? We need the smallest safe remedy; no application build has started.
2 Replies
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Update: we created a new private GitHub repository containing the exact sealed candidate and connected the official Railway GitHub App with access restricted to that single repository. This rules out the missing local commit / manual upload path.
Repository: phantomousebabe-ctrl/evertale-release-b-deploy
Branch: release/release-b-197fd1cf
Commit: 6bde2ba6b1ad4e24d89e89fc81a64306304c959e
Independent fresh clone verified 684 files, 90,918,969 bytes, and the same fingerprint 197fd1cf71e07c02ca64285dce0a1ae7ac3e5f2406e01076bf3724be082245d8.
Connecting ONLY an isolated staging service automatically created deployment fc5d4a2b-0846-43c6-b5f5-67402b85d44b from that exact repo/branch/commit. It then stopped at INITIALIZING before build; deploymentStopped=true, source still reports null, and no staging domain or runtime was created. No production resource was changed.
Please investigate why Railway cannot initialize a GitHub-source deployment as well as local source uploads, and provide the platform-side diagnostic / smallest remedy.
2 months ago
A correction from our records that should unblock you: the GitHub-sourced deployment you created at 12:43 UTC from evertale-release-b-deploy did not stop at initializing. It completed successfully at 12:44 and produced a built image. If the dashboard showed Initializing when you checked, that was mid-flight, and a public domain only appears once you generate one on the service.
Your railway up uploads are a different story. Those failed on our side at the snapshot step, first during Monday evening's incidents (https://status.railway.com/incident/YYU63JUO) and again today, and your archive is not the problem. The attempt from last night that still shows Initializing is inert and is not blocking your newer deploys.
The GitHub connection you set up is the working path, and it carried the exact commit you sealed.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago