@HenrikJoreteg It’s fine, I’m an unashamed jerk most of the time, and I understand you don’t want to hear from a nobody, you want an informed response from a Netlify engineer.
However I understand the problem enough to know that even though it’s annoyingly intermittent you should be capable of proving what you suspect on your side.
I also know the steps I suggested for checking seem utterly stupid, but I’ll outline them again:
- When you spot a fresh occurrence in your GCP logs, try to access that file URL directly, repeatedly, perhaps different locations, incognito etc. Either the response is consistent, or it isn’t, I’d expect it to be consistent and always return the contents of your
/index.html. - Use the File Browser on the latest deployment to confirm if the file exists.
If the requests were made after the latest deployment, the file exists and requests for it are returning (even intermittently) the contents of the /index.html, then you’re right and you’ve got proof.
If the file doesn’t exist then you would need to investigate other avenues, like locally cached pages making requests for the stale asset paths.
It’s definitely worth posting, it’s just unfortunately not a super active community.
Edit: For what it’s worth, I’m the most active non-Netlify community member currently and I’ve not spotted anyone else raise it. Usually when people have raised similar issues it’s eventually been determined to be their cache strategy or custom service workers they’re running.
Apologies too if what I’ve suggested is something you’ve already checked, or is otherwise negated by something I haven’t considered, like some custom caching scheme or obscene middleware.