Intermittent errors with Gatsby Cloud builds
See original GitHub issueI’m getting this error occasionally with Gatsby Cloud builds. Triggering a new build usually results in another build that is successful without errors.
[typegen] An error on codegen GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbySanityImageFixed". GraphQLDocumentError: Unknown fragment "GatsbySanityImageFixed". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFixed". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbySanityImageFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbySanityImageFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbySanityImageFluid". GraphQLDocumentError: Unknown fragment "GatsbyImageSharpFluid". GraphQLDocumentError: Unknown fragment "GatsbySanityImageFluid".
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Gatsby Cloud builds failing : r/gatsbyjs - Reddit
I have a couple of gatsby sites in Gatsby Cloud and since a few days back, they are failing to build. It's always...
Read more >Troubleshooting Common Errors - Gatsby
Problems with the cache · Errors with common plugin configurations. Installing plugins for styling results in Generating SSR bundle failed · Errors in...
Read more >Gatsby Build error failed to generate Javascript and CSS ...
I want to know why I am getting this error trying to build this website through Netlify and Gatsby Cloud. The build works...
Read more >5 Optimizations to Get Faster Gatsby Builds Today - Netlify
Make sure your source images aren't huge. Gatsby has to process images during the build, so bigger images mean slower builds. Check your...
Read more >Gatsby Cloud - Customers experiencing latency and ... - IsDown
Customers experiencing latency and intermittent website downtime · Monitor Gatsby Cloud and all your third-party dependencies in one place.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve experienced the same error as you. In my case, I could only see this error after having a
gatsby clean
and trying to dogatsby build
(without runninggatsby dev
beforehand)Try to change the order on how you load the plugin in
gatsby-config
. In my case, moving it at the end of the array solved the issue.Good luck 👍
Hi @Samic8,
I was off here for months but now started over. You can watch the progress at #138. I’m going to change the behavior, so I don’t recommend code contribution for now. But I will request you to test when the pre-release is ready.