Hi everyone! I wanted to let you know that we’re aware of this issue and are actively working on a fix.
We conducted an investigation and discovered that this issue occurs when you have a project with sections and make a request with a pagination limit. If at any time the limit you specified coincides with the end of a section, the pagination ends early. This is the bug we have identified.
Here’s an example explanation of a scenario when this will happen:
- PROJECT_A has a section called SECTION_1
- PROJECT_A has a section called SECTION_2
- SECTION_1 has 5 tasks
- SECTION_2 has 10 tasks
- You make an API call to Get multiple tasks endpoint and specify a limit of 5 the API will return
next_pageof null after those 5 tasks → technically this should not happen and it should return 15 tasks, so this is the bug that we are currently fixing.
I’ve provided a similar explanation in this comment Problem with next_page
Thanks @Phil_Seeman for flagging this to us