Internal Error with GraphQL (metaobjects)

Retired Boards Appdev Custom Storefronts
1 
Internal error. Looks like something went wrong on our end. Request ID: c26c4afb-a8e1-4e05-93d8-9901b0df0cc8

I get this output when trying the following code:

metaobjects(type: "car-manufacturer") {
            edges {
                node {
                    field(key: "name") {
                        value
                    }
                }
            }
            
        }

I was trying to output the values for car-manufacturer.name

FYI: I have 80 entries for car manufacturers and I’m very new to GraphQL so I’m still figuring this out. Please give me a hint at what I’m doing wrong.

2

Solution:
I had to add the parameter “first: 250,” to the metaobjects function to limit the amount of returned objects.
It seems, that the documentation isn’t really good for this query as it didn’t mention this.

3

Hey @carhifi

We were previously chatting in this thread and it’s great to see you found the solution to the GraphQL error! Overall have you solved the issue with the 128 meta-objects limit, or have you found a workaround?

If you send us a ticket regarding our documentation not addressing the issue of the limit of returned objects then we can send that up to our developers to improve the documentation.

I’m no expert but it’s possible that adding the “first” parameter with a value of 250 helped to limit the number of objects returned and resolved the internal error. This is because the GraphQL server might have been struggling to process a large number of objects in the response, and setting a limit using the “first” parameter can help to mitigate this.

In general, it’s a good practice to limit the number of objects returned in a GraphQL query to avoid overwhelming the server or causing unnecessary network congestion.

Best,