Had to republish a document to invalidate CDN cache. Now it works!
1 Like
Great to hear you got it working this extra information is really helpful.
I'm really sorry this occurred in the first place.
I was also asked to republish a document and it seems to have fixed it for me now, too
Seems like the fix is only temporary. After a while it's broken again :((
OK, damn. We just got the same feedback internally and the team is still working on this to get it resolved. I can only apologise while the team is working hard, so sorry again.
OK, everybody. The latest word is that it should be all good now!
Jep looks good for me for now. Fingers crossed it stays that way 
1 Like
I'm sure it will now the team is on top of this. Thanks everyone for your patience 
These CORS issues can be tricky to identify because the majority of the time they are thrown by the browser when a GraphQL query is too large. Hopefully, we can do some work there as well so that the browser can give better error messaging for that case.
Let us know if you see any other issue and we'll be quick to jump on it.
Thanks again.
I definitely can relate that CORS issues are thrown very randomly by browsers for unrelated issues... But the query being to large is kind of a home made issue, with your insistance on using GET requests instead of POST for graphql right 
That's true, the original idea being to limit query size to improve performance. I know there are plans to open the GraphQL API to POST requests, although it's not being work on right now.
We need to take time to consider that option correctly because just allowing huge queries will put a lot of strain on the API.
Thanks guys! Can confirm it's working now
Issue resolved.