# Search API: Lack of pagination leads to limited results

**URL:** <https://forum.asana.com/t/search-api-lack-of-pagination-leads-to-limited-results/60110>\
**Category:** API & Developers\
**Created:** [13 September 2019 22:21 UTC](https://forum.asana.com/t/search-api-lack-of-pagination-leads-to-limited-results/60110 "2019-09-13T22:21:08Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![rocco.haro](https://luna1.co/8d76cd.png) [@rocco.haro](https://forum.asana.com/u/rocco.haro)\
**Post date:** [13 September 2019 22:21 UTC](https://forum.asana.com/t/search-api-lack-of-pagination-leads-to-limited-results/60110/1 "2019-09-13T22:21:08Z")

</div>

Thanks in advance.

I’ve read through the docs, and in the process of writing some code to use the search API. While writing some tests, I discovered a scenario that leads to lack of information.

Context:  
We are using the search API to filter through tasks that fall under a particular section, and have a particular modified\_at.after & modified\_at.before window. We implement a sliding window of time to retrieve more tasks that may exist but are not returned since we are limited by 100 tasks, and no ‘next\_page’ field is returned by the search API. This is fine, but then I realized that there exists a scenario the sliding window implementation will not work, and we can not use any other existing filters to capture other tasks.

Problem:  
Let’s say section 1 contains a 101 tasks, and by some chance all of the these tasks were modified at the same time by different users. With my current filter and sliding window implementation, I will never be able to get the 101th \> task.

I know the scenario is unlikely, but even unlikely things happen. What do you guys propose I do to capture those hanging tasks?

---

_[View the full topic](https://forum.asana.com/t/search-api-lack-of-pagination-leads-to-limited-results/60110)._