11 days ago
Subject: GitHub sync broken - service can't see new commits, keeps deploying an old commit
Project: virtuous-amazement (id: d319650b-1c5f-4af8-b723-69025ab88a76)
Environment: production (id: f52f3025-44b4-45e7-8996-5ee1434b11e2)
Service: future-ip-website-v2 (id: acf5072c-528b-424b-a665-5e559c7c028f)
Repo (private): Richardvandev/future-ip-website-v2
Branch: main | Auto-deploy: on | Wait for CI: off | Region: EU West (Amsterdam)
PROBLEM
Every deployment (auto-deploy, manual Redeploy, new pushes) builds an OLD
commit (177720d "Privacy: Railway-hosting...") instead of the current HEAD
of main. The service simply never picks up newer commits.
PROOF
GitHub reports main HEAD = e31eb0076d802d03524bd019c2d5b24e369efdb8
(verified with git ls-remote origin refs/heads/main).
But Railway's own API cannot find that commit. Calling:
mutation { serviceInstanceDeployV2(serviceId, environmentId,
commitSha: "e31eb0076d802d03524bd019c2d5b24e369efdb8") }returns:
"No commit found for SHA: e31eb0076d802d03524bd019c2d5b24e369efdb8"
The latest 3 deployments all show commit 177720d. So Railway's internal
mirror of this repo is stuck several commits behind GitHub.
WHAT I ALREADY TRIED (none worked)
-
Manual Redeploy (multiple times)
-
Empty commit + a real commit with file changes
-
Disconnect/reconnect the branch (main)
-
Fully disconnect/reconnect the GitHub repo + branch
-
Refreshed the Railway GitHub App installation (repo access confirmed:
the app has access to Richardvandev/future-ip-website-v2)
-
API deploy via serviceInstanceDeployV2 with the commit SHA (returns the
"No commit found" error above)
Note: this started around a Railway incident ("Logs and metrics may be slow")
and shortly after migrating this service + its MySQL volume to EU West.
REQUEST
Please re-sync this service's GitHub integration so it sees the current HEAD
of main (e31eb00) and deploys it. There appears to be a stale internal repo
mirror for this service. Thank you.
4 Replies
Status changed to Awaiting Railway Response Railway • 11 days ago
11 days ago
Thanks for the detailed report, and sorry for the repeated trouble here. This is separate from the current build slowness on our side. Your service is pinned to a stale internal copy of your repo, which is why every deploy rebuilds the old commit and why a deploy by the new commit SHA comes back as not found even though it is the live HEAD on GitHub. None of the self-serve steps you tried will clear this, since the fix is a re-sync of that internal copy from our end. We are getting that refreshed so the service can see your current HEAD on main and deploy it, and we will follow up here once it is done. If anything changes on your side in the meantime, just reply on this thread.
Status changed to Awaiting User Response Railway • 11 days ago
noahd
Thanks for the detailed report, and sorry for the repeated trouble here. This is separate from the current build slowness on our side. Your service is pinned to a stale internal copy of your repo, which is why every deploy rebuilds the old commit and why a deploy by the new commit SHA comes back as not found even though it is the live HEAD on GitHub. None of the self-serve steps you tried will clear this, since the fix is a re-sync of that internal copy from our end. We are getting that refreshed so the service can see your current HEAD on main and deploy it, and we will follow up here once it is done. If anything changes on your side in the meantime, just reply on this thread.
4 days ago
How long more will it take till its done?
Status changed to Awaiting Railway Response Railway • 4 days ago
3 days ago
This thread has been opened as a public bounty so the community can help solve it. The thread and any further activity are now visible to everyone.
Status changed to Open Railway • 3 days ago
3 days ago
Try clicking on your service, press Ctrl/Cmd + K, and deploy latest commit.
0x5b62656e5d
Try clicking on your service, press Ctrl/Cmd + K, and deploy latest commit.
3 days ago
Hi team,
It has now been over a week since you confirmed this is a stale internal repo mirror on your side and said you would "get that refreshed." Nothing has changed — the service still deploys commit 177720d instead of the current HEAD e31eb00.
I also just tried the Cmd+K → "deploy latest commit" suggestion from the moderator. Same result: it deploys the old "Privacy" commit again.
To be clear about what has been attempted (all unsuccessful):
Manual Redeploy (10+ times over the past week)
Cmd+K → deploy latest commit
Pushing new commits (empty and with real changes)
Disconnecting/reconnecting the branch
Fully disconnecting/reconnecting the GitHub repo
Refreshing the Railway GitHub App installation (toggling repo access)
API call serviceInstanceDeployV2 with the correct SHA → returns "No commit found"
None of these self-serve steps can fix this — you confirmed that yourself. The fix requires a re-sync of your internal repo mirror from your end.
I am a paying Pro customer and my production service has been unable to deploy new code for over a week. This is blocking my business. I need this resolved — not handed off to a public bounty.
Please prioritize the re-sync of the internal repo mirror for service acf5072c-528b-424b-a665-5e559c7c028f so it picks up the current HEAD of main. If there is a reason this is taking longer than expected, please communicate a timeline.
Thank you.