BulkOrders returns INTERNAL_SERVER_ERROR with any query

Technical Q&A
1

Hi,

We’re getting INTERNAL_SERVER_ERROR for all bulk orders queries for our App, and it doesn’t seem to matter which kind of query we send.

The app id is

gid://shopify/App/6878599

We don’t have access to chat for some reason anymore, so any help is urgently required

2

Hello @sniffiedev

Review your app’s logs to see if there are any error messages or stack traces that can provide insight into what’s causing the issue. You can view your app’s logs by accessing your app’s Heroku dashboard or using a logging tool like Loggly.

Try testing your app’s API requests using a tool like Postman or cURL to see if you’re able to replicate the INTERNAL_SERVER_ERROR. If you’re able to replicate the issue, it may help to isolate the problematic API endpoint or request.

If you’re unable to resolve the issue on your own, I recommend reaching out to Shopify’s Partner Support team via email or submitting a support request through the Shopify Partner Dashboard. They may be able to provide additional guidance and help you troubleshoot the issue.

3

The issue is with the new API versions after 2022-07.
It requires one to make an additional request to Shopify to access PII information in the Orders API, even if one does not need or want to access them(the PII info specifically). Meaning, if you want access Orders, you need to request (in addition to defining read_orders scope) it and tell them why you want it, and what are you going to do with the PII info, no matter whether you actually even fetch or handle it. Seems like a poor design choice, and unclear specs on that part. Or maybe the feature just doesn’t work correctly. And, in addition, we are unable to submit the request, as the page that asks the details complains about a “missing explanation” for a field that does not exist. We sent an email instead, hoping to either get the request page fixed, or just have them grant access to the orders with the new api. In the meantime we’re using 2022-07 for Orders to go around the issue, the downside with that being that it is decommissioned in July.

Hope this helps someone else struggling with the same issues, and prevents you from wasting your time trying to figure out what’s wrong.