You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error: The result of this StaticQuery could not be fetched.
This is likely a bug in Gatsby and if refreshing the page does not fix it, please open an issue in (https://github.com/gatsbyjs/gatsby/issues)
Production environment
White page in some clients
Mobile client for the most part
Steps to reproduce
Impossible to reproduce, because it never happens in development with gatsby develop, gatsby build and gatsby serve, neither in an NGINX instance in a Docker container and neither in browser with incognito mode (production).
Why the issue only happens in production? - this issue is causing economic losses for us because we do not have the full availability of our website for our users. We can't keep sending hot-fix to production and check with our users if the issue still persists. We are up-to-date with gatsby and other npm packages. We are working with queries described in the documentation. What more do we need??
The text was updated successfully, but these errors were encountered:
Hi, thanks for the issue! Sadly we can't do much without a reproduction and thus this issue is not actionable. You can follow #26563 or comment there when you have a reproduction. Thanks!
Description
Error: The result of this StaticQuery could not be fetched.
This is likely a bug in Gatsby and if refreshing the page does not fix it, please open an issue in (https://github.com/gatsbyjs/gatsby/issues)
Steps to reproduce
Impossible to reproduce, because it never happens in development with
gatsby develop
,gatsby build
andgatsby serve
, neither in an NGINX instance in a Docker container and neither in browser with incognito mode (production).Expected result
Load the content of the pages
Actual result
White screen on some route pages
Environment
One further comment
Why the issue only happens in production? - this issue is causing economic losses for us because we do not have the full availability of our website for our users. We can't keep sending hot-fix to production and check with our users if the issue still persists. We are up-to-date with gatsby and other npm packages. We are working with queries described in the documentation. What more do we need??
The text was updated successfully, but these errors were encountered: