13 days ago
I've pushe dseveral updates to my code via GitHub (repo guivilar07/rota-automatica, branch main), and Railway always shows "Deployment successful" with the container starting normally in the logs. However, the content actually served publicly never changes — it is always byte-for-byte identical, regardless of the commit.
What I've already tested and ruled out:
- Build cache ("Skipped Builds" is OFF)
- CDN Caching (OFF)
- A brand-new domain generated for the same service (still served the old content)
- A brand-new service, created from scratch, connected to the same GitHub repo, on its very first build (still served the exact same old content)
I confirmed via the official GitHub API (api.github.com/repos/guivilar07/rota-automatica/contents/app.py?ref=main) that the correct, up-to-date file is present in the repo. Despite that, both the original service and the brand-new service serve an outdated version of app.py.
This points to a problem between my Railway account and the GitHub repo connection (possibly the installed GitHub App, or some infrastructure-level cache stuck on an old version of the repo). This has been happening since yesterday, starting right after a code push late in the day.
I found a very similar solved thread on this forum (station.railway.com/questions/deployments-show-successful-with-corre-2eb90423) where a moderator's suggested fix was to unlink and relink the GitHub repo, then use "Deploy Latest Commit" via the Command Palette. I'm about to try that, but wanted to reporShort test sentence without special chars.t this in case it's a wider issue.
Project: zippy-light
Service: web (and a second test service: rota-automatica)
Environment: production
4 Replies
13 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 13 days ago
13 days ago
Hello
Can you verify on the Doployment Tab of the App:
When you click onto the Card under "Deployed via Github" where your commit from what the deploys code is going from, is the same commit as the latest in your repo?
Attachments
13 days ago
try Double checking the deploy actually hits production, then try purging the CDN cache or redeploy fresh. Sometimes stale content sticks around.
13 days ago
Are you running two railway services pointing at the same repo? I ran into that and it was serving the old ENV VARS an old commits both are connected by deleting the extra service and reconnecting the GitHub app fixed it for me.
13 days ago
question also by any chance, did you fully remove the domain in front of the old railway service before adding it to the new one and did railway actually issue a new SSL cert for it if no remove the domain from the old service first when you do that re-add the new one so it can force a fresh cert and DNS bind. That would likely confirm if it’s the stale binding, causing it.