New behaviour: unexpected cache after deploy

Support
,
1

Hi all,
Our Gatsby site (https://hutch-dev.netlify.app/) is deployed with continuous builds from storyblok through a webhook trigger. The code is on github. When our client clicks the execute button in storyblok, a new build is triggered, and the site is deployed and everything is magic. Or was.

Recently (the last month or so), and with no code or setting changes on any platform (netlify, storyblok or GitHub), our client has reported that it can take an hour before they see their changes on the website. Not good for them when they want to correct a typo in a blog.

We have checked to see if this is a local browser cache and it appears not to be. Eg, using a device that has never loaded the site before still loads the “old” version after a deploy and updates are not seen for an unusual amount of time.

We also do not, and never have, use a serviceworker or offline plugin.

It’s also strange that this behaviour did not exist a few months ago, and as I said, there have not been any codebase or settings changes in that time.

When I trigger a deploy from the netlify dashboard, and use the option to clear the server cache, then it takes a little longer to rebuild and deploy, but the changes are seen within 4 or 5 minutes.

Has anybody else experienced this sort of behaviour, and what is the best way to ensure netlify is not serving old content after a deploy?

2

Hiya @richythings and sorry to hear about the trouble!

Could you please get an x-nf-request-id for me for a wrong asset you see served after deploy? This article describes how: [Support Guide] Netlify Support asked for the 'x-nf-request-id' header? What is it and how do I find it? . That’s the detail we’ll need to understand if we served the wrong thing, or if it was browser cache.

The “clear cache and deploy” in our UI is ONLY the build cache - it’s not the network cache that browsers use - so any difference in behavior using that button is probably not caused by the use of the button specifically, since every production deploy, when completed (you see the message “Site is live” in the build logs), clears the network cache.

Thanks in advance for your help in troubleshooting!

3

we had this same issue when we had netlify-plugin-gatsby-cache enabled, it used to work, but then the past month or more it stopped so we had to remove the plugin.

only full builds with no-cache seemed to work.

it never seemed to be able to pick up changes made in storyblok.

4

hi @enginedigital , sorry to be slow to get back to you! can you tell us what version numbers you are using? a package.json would be helpful, as well as a link to a full deploy log.