Orders before a certain date are all inaccessible through the API even with read_all_orders scope

[dbright]

I maintain an unlisted app that pulls new orders through the API and am trying to debug an issue with an order placed for a certain merchant back in early June. When trying to access the order, however, I get a 404 even though the merchant can view the order and the URL of the order page implies that the order should exist at the endpoint I'm checking.

I've double checked with support that my app does have access to the read_all_orders scope so it's not a permissions issue. That said, for this one merchant only, every order before June 29th (from memory, may be off a day or two) 404s while I can retrieve every order after that date.

To be clear, I can access older orders from other merchants using the app with no issues. Shopify support suggested I posted here and thought it might be an issue with another app that is somehow affecting access to the order.

I'm out of ideas for how to attack this problem. Does anyone have any tips for how I might go about figuring out how these orders have become inaccessible and hopefully fixing the situation?

[CalD]

Hey @dbright,

Can you provide the X-Request-Id from the response headers for an unsuccessful call (and a successful call, to potentially narrow down any issues with another app) so we can troubleshoot further?

[dbright]

Hi Callum,

Thanks for the reply and your patience while I got this info for you. I just re-ran the request and the X-Request-Id is 9c360d44-9fe2-49fe-902c-cf9702f26f6e . Please let me know if there's anything else I can get you that might be helpful.

Thanks,

Doug

[_JB]

Hey @dbright,

I just checked this request and can confirm your app doesn't have the `read_all_orders` scope for this shop. I can see your app has been granted permission to use the scope, but you will still need to request the scope during install. If you were granted permission to use the scope after install, you can update the scopes for any existing installations by redirecting the user back to the Oauth screen. More details are available in our docs here.