6 months ago
Hello Railway Support Team,
We are facing a persistent issue with our deployment pipeline for the following service:
* Project ID: c254488a-1e57-40a3-8e4a-dd3c7a64552d
* Service ID: db9ee7c8-a9dd-4a8d-ba29-9f2f3c4fb326
The Problem:
The deployment for this service appears to be stuck on an old commit. Despite numerous new pushes to our master branch and attempting manual
deploys from the latest commit hashes, the running application is not updating.
Evidence:
The primary symptom is that our deployed frontend is still making an incorrect API call to /api/api/users/login. This was a bug in an old version
of our code. We have since pushed multiple fixes, including:
1. Correcting the frontend API client logic.
2. Setting the VITE_API_URL environment variable correctly.
3. Pushing cache-busting commits by adding comments to frontend files.
4. Even adding a JavaScript alert() to our main.tsx file to verify the deployment of new code, which never appeared.
This proves that Railway's build process is continuously serving a stale, cached version of our frontend assets and is not picking up the latest
commits from the master branch.
Our Request:
Could you please manually clear the build cache for our service? We believe this is the only way to force the deployment pipeline to fetch and
build the latest version of our code from the repository. Our latest clean commit is 1056f9f.
Thank you for your help.
5 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
🧵 Service deployment stuck in "Queued: Waiting for volume migration"
🧵 Deployments stuck in "Queued. Waiting for deployment slot"
If you find the answer from one of these, please let us know by solving the thread!
6 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 6 months ago
6 months ago
Hi niyaz0912,
Railway does not keep a build cache. This is an issue with your application. Is it possible you're pushing on a different branch? Does the latest commit message show up on the deployment?
6 months ago
Please remember that AI generated responses are not tolerated here. Your response is nonsense. As I said in the previous comment, Railway does not keep a cache of this sort. None of these potential solutions will fix anything.
6 months ago
are you using docker? is it possible that I need to update a build variable that you forget?
6 months ago
Sounds like static asset caching somewhere, either by the browser or by a CDN.
Vite adds hashes to the static assets by default. In the Railway build logs, Expand the log entry with the Vite build and you can see the filenames there. Then you can try compare the filenames to those of the static assets served up when you visit the site. That will tell you if Railway is serving up an old commit or if it's somewhere else.
Then you can try download one of the newer assets directly. Grab the filename from the build log and then try download it, something like https://your-app.com/assets/index-q6Vw-v9F.js.
Disable any CDN that may be serving up old content (e.g. Cloudflare proxy)