a month ago
Hi Railway team,
Since 2026-09-10 ~12:04 UTC, deployments for two services in my project have been failing at the Snapshot Code stage with:
[ERROR] ##NOT-FOUND## repository not found
Project: lucid-endurance (ef827493-fd7e-4227-9e6f-a3399bd1f9db)
Environment: production (ca46b72f-4aab-4f69-a294-78f8ba3f833f)
Affected services:
javasmedia-site (dcaf551f-7aba-419a-8bcb-f819b118c41b)
javasmedia-backend (e5aba121-9bcb-423e-835e-1a4b8ad09a03)
Both source from the same GitHub repo: amirahmed96/javasmedia-website, branch main.
What I've already verified/tried:
Repo is confirmed Public (checked repo Settings → Danger Zone directly)
Railway's GitHub App installation has "All repositories" access and is not suspended (checked github.com/settings/installations directly)
Disconnected and reconnected the Source Repo in each service's Settings — the UI now shows a clean connection (no error in Settings), but new deployments still fail with the exact same error
Waited several hours (from ~12:04 UTC to ~15:18 UTC) — issue persists, latest failed attempt: deployment 25945cbc-a476-470d-822c-996744e130f6 (site) / a6a560d7-7695-44d1-a30a-65b77c6dd7d4 (backend)
My GitHub account (amirahmed96) is new (~3 weeks old) with high automated commit volume this month — I suspect this may be related to some GitHub-side restriction on cross-app repo access, but I have no visibility to confirm this from my end.
Since everything checks out correctly on my side (public repo, correct App permissions, clean reconnect) yet the deploy pipeline still can't snapshot the code, I'd appreciate help investigating from your backend logs.
Thanks!
1 Replies
Status changed to Awaiting Railway Response Railway • 26 days ago
25 days ago
Your GitHub account isn't resolving publicly, and that's what's breaking the deploys. Your profile and the repo both return 404 to anyone who isn't signed in as you, so everything looks fine from inside your account while our builder gets nothing back. Our GitHub App can't find an installation for the repo either.
You were right that this is a GitHub-side restriction. It's not something we can lift from here, and GitHub Support is the only place that can tell you why the account is in that state.
If you need to ship before then, push the code to a repo under a different GitHub account and point the services at that.
Status changed to Awaiting User Response Railway • 25 days ago
18 days 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 • 18 days ago