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?