A space to discuss GraphQL queries, mutations, troubleshooting, throttling, and best practices.
Hi! I am migrating to cursor pagination and when I make a request to
https://mhengineering.myshopify.com/admin/api/2020-01/customer_saved_searches/2231682133/customers.json?limit=250
I get the following Link header
<https://mhengineering.myshopify.com/admin/api/2020-01/customer_saved_searches/2231682133/customers.json?limit=250&page_info=eyJxdWVyeSI6ImNvdW50cnk6XCJBcmdlbnRpbmFcIiIsImxhc3RfaWQiOjEwMzc1NzU4NDc5ODAsImxhc3RfdmFsdWUiOjE1NDk4OTg4OTAwMDAsImRpcmVjdGlvbiI6Im5leHQifQ>; rel="next"
the issue is as follows:
When I make a request to get the next page using the URL obtained by the Link header I don't get results, instead I receive
{ "errors": { "query": "query cannot be passed when page_info is present. See https://help.shopify.com/api/guides/paginated-rest-results for more information." }
}
It is weird because i tested the cursor pagination with Customers, Orders and Products endpoints and it works fine.
Does anyone have any idea what's going on? Thanks in advance
Hey @mhengineering ,
Thanks for bringing this up. This is a known bug on our end, and our developer teams are looking into this. I'll provide more information when I can.
To learn more visit the Shopify Help Center or the Community Blog.
Any idea when this will be fixed? It has already been 3 weeks and I'm still running into this same problem.
I am having the same issue - my app uses this functionality and we can't migrate to cursor based pagination until this is fixed.
Following up on this - is there an ETA on when this will be fixed?
Hey @WOTIO ,
I cannot provide any ETA at this point for when this will be fixed, but I can assure you this issue is still on our radar and is properly prioritized. As soon as I have more information to share, I will update this thread.
To learn more visit the Shopify Help Center or the Community Blog.
Thank you. I hope it is resolved before the July 1 deadline.
Hi @hassain - We are coming down to the wire on timing to get this fixed before we either remove a critical and highly used piece of our app, or our app is removed from the App store. Can you give me an update please?
@WOTIO it appears the fix might have been published.
I was just doing some tests on a small list and it appeared to work.
@shopSketch @Thank you for the heads up. I will test this morning!
@shopSketch I have confirmed it is working now. Thank you to @hassain and team for getting this pushed out before the deadline!!