4 months ago
Hi Railway team,
I'm experiencing a persistent build cache issue where my deployed code doesn't match what's in GitHub, despite multiple deployment attempts.
What I've tried (all failed):
1. 4x Git push with new commits
2. 2x Complete service reset (deleted & recreated)
3. 1x Dummy commit (README change)
4. 1x GitHub repo disconnect + reconnect (relink)
Total: 8 deployment attempts - all deployed old code version.
Evidence old version is running:
- GitHub shows: Enhanced logging, file validation, full error output
- Railway logs show: None of these features
- Output quality shows: Missing improvements from latest code
Setup:
- Python/FastAPI app with FFmpeg processing
- GitHub: Multi-Kamera/videosync-processor (main branch)
- Railway: Hobby plan, Docker deployment
Question:
Is there a way to force Railway to completely clear build cache and deploy fresh code from GitHub? The repo relink didn't help.
Any suggestions appreciated!
1 Replies
4 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 [Settings.py](Settings.py) not updating despite new deployments - Caching issue?
🧵 URGENT: Deployments successful but Railway CDN serving cached frontend files
If you find the answer from one of these, please let us know by solving the thread!