New behaviour: unexpected cache after deploy

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!