I’m building a Custom App and I see the app review prerequisites require configuring pagination. I’m working through this doc to configure my modules: Pagination | Make Apps
However I’m unsure how to actually use the pagination settings I’m adding to my app in a Scenario. The only pagination guide I could find is this: https://www.msquare.pro/post/api-pagination
But from what I can tell, this guide works regardless of whether the Module has embedded pagination or not.
Our APIs are a mix of pagination with next_page_tokens and num & start style. I’m starting with next_page_token style.
The Make docs say: In every following request, we’ll use the nextPageToken provided with the previous one. We’ll stop the pagination when no other nextPageToken was received.
This makes me think it’s a native feature I can enable in my Custom App and Make will automatically process the pagination until there are no tokens left. I can’t figure out how to create this directive though.
At first, you seem to have done correctly. What is the behavior of the module? Does it break? returns you only 1 page?
One way to debug it is to use the Make Dev tool (Make dev tool) and to debug the calls the module is doing. It will help you see whether the next_page_token is here or not in the response and wheter it’s picked by the module or not.
If you never used it, here is an example of what the dev tool looks like
The current behavior is the Module only makes 1 call which gets the initial page. There doesn’t appear to be any automated attempt to get the next page.
And I’m not sure how to direct my Scenario to keep getting pages outside of that tutorial I posted earlier which is a separate thing from what I can tell.
If I add a duplicate of the Module after the first instance, it just runs the same initial call to grab the first page.
Is there a way to direct Make to use the pagination configured in the Module settings?
I haven’t tried the Make Dev Tool yet since I don’t have Chrome installed at the moment. At this point, I don’t think there’s much to debug there anyway because my Scenario is only grabbing the first page and not trying anything else. I can try that if you think it’s necessary to track down whether a second call is being made for pagination.
The way you configured the module should have Make grab automatically the next pages.
The DevTool can be interesting to see with more details what the module sends for the request and what it gets back from the API.
I suspect there is something wrong with the condition.