Hello,
We are intermittently receiving the following error on our getOrders GraphQL requests: “Internal error. Looks like something went wrong on our end.”
This appears to happen randomly every other day, but we recently saw a significant spike. Could you help us investigate the root cause using the request IDs below?
We would also like to know whether there is anything we should change on our side to reduce or avoid these errors, such as query structure, rate limiting, pagination, retry behavior, or request timing.
Request IDs:
- 67a309ec-5cd8-409b-bb8f-fc439d29e583-1777305962
- 4a81f9da-8b2f-4ce3-ae9d-c427e98c033b-1777305961
- 4460ef85-4ec1-4a10-9800-6f4c9ee23ea3-1777305958
- 3ab516bd-6737-43a4-8f5b-729416e2ad45-1777305786
- fc426965-9ac1-4285-80b9-00c7653cff8f-1777305781
Thank you.
Hey @Chen_Shanhan, I checked the request IDs you shared and they line up with a brief Shopify-side service issue around that time.
For the examples I could trace, the requests reached the GraphQL Admin API and returned HTTP 200, but the GraphQL response contained INTERNAL_SERVER_ERROR. The evidence for those request IDs points to the service issue rather than the query shape, pagination, rate limiting, or request timing.
That issue has since been mitigated. Your app should still treat intermittent server-side GraphQL errors as retryable and use exponential backoff. I would keep the GetOrders query as-is based on these request IDs.
If this shows up again outside that window, share fresh request IDs and timestamps and we can check whether it is the same pattern or a new issue. Thanks for raising this with us!