Gatsby page-data.json inconsitently causes 404

We’ve had some deploys go out where seemingly the atomic deploys aren’t working right and some files are missing, but not for every edge node - so some users get a working page, but others see a 404.

So you get Gatsby’s SSR version of the page, and then it fails when react takes over and tries to hydrate.

How can we prevent this, or resolve it when it happens. Currently we just keep poking things and running more builds until it sorts itself out, which isn’t sustainable.

hmm, that’s frustrating. Do you have a sitname to share with us? Any errors in your build logs?