My client has access to their GitHub but don’t have any access to the netlify account associated with the site. They were recently able to upload a batch of changes, but the second batch seems to not be showing up due to a caching issue. I have seen in this support forum that clearing the cache is easy from the deploys menu, unfortunately, the client cannot even get to the deploys menu in netlify at all. They have no access to this build on netlify. Can we just request a simple cache clear from netlify somehow? Ideally they need access to their site, but for now they are just on a deadline to share this site with their leadership.
All new production deploys of sites at Netlify clear the cache for the site in the ADN nodes.
The “clear cache” button in the web UI clears a local storage cache used by the build system. The cache isn’t the same cache as the deployed files of the site on the ADN.
The cache that the button clears contains things like node modules, ruby gems, etc. It contains build dependencies reloaded between builds to save time on the dependency install (reusing the dependencies of a previous build so only dependencies that change need to be reinstalled). (It can contain anything theoretically but it is still distinctly separate from the caching on the ADN.)
Long story short, if you push a change to the upstream Git repo, this should clear the deployed site cache when the new deploy is published.
If you send us a URL for an asset which isn’t being updated we can confirm if it matches the currently published deploy or not.
You can post that information publicly or you can private message (PM) that to one of our support staff. I’ve confirmed that PMs are enabled for your community login. Please keep in mind that only one person can see the PM and this will likely mean a slower reply than posting the information publicly. Please feel free to reply to however you prefer though.
@markitecture How certain are you that this isn’t a local caching issue?
We are pretty positive it’s not a local issue. Checked on two different machines, two browsers each, two different networks, etc.
Hi, @markitecture. There have been no new deploys of that site since May 17th, 2021. When I test, all CDN nodes are returning that version of the site (the May 17th version).
There have been three attempted deploys since then, however. All three of those builds exited with errors and builds with errors are not published.
We would recommend that a member of the Netlify team for this site login and review the build logs to resolve the build errors. Once the builds are succeeding, they will be published and the updates will be available on the deployed site.
If there are questions about this, please let us know.