# Pagination in Workflows with Large Numbers of Users **URL:** \ **Category:** Templates\ **Created:** [November 20, 2025, 5:23pm UTC](https://devforum.okta.com/t/pagination-in-workflows-with-large-numbers-of-users/34611 "2025-11-20T17:23:48Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![dylanbarker](https://avatars.discourse-cdn.com/v4/letter/d/c67d28/32.png) [@dylanbarker](https://devforum.okta.com/u/dylanbarker)\ **Post date:** [November 20, 2025, 5:23pm UTC](https://devforum.okta.com/t/pagination-in-workflows-with-large-numbers-of-users/34611/1 "2025-11-20T17:23:48Z")
Workflows can handle any paginated API, check out Max and Ajay’s video explaining how this works: [https://www.youtube.com/watch?v=zqzTcOrCV9k](https://www.youtube.com/watch?v=zqzTcOrCV9k) Attached is a template for paginated API operations using the Okta connector. We had a use case where the client had 10 M users in Okta and we needed to read each user and collect statistics on a weekly basis. Streaming is limited to 1 M users every 25 hours so we needed to user pagination. Through testing I found that using an asynchronous Call Flow card to pass records to a helper flow significantly increased the speed of pagination as the main pagination workflow is able to loop extremely fast without waiting for records to finish processing in the helper flows. \*Note: There’s a recursion limit of 250 pages in workflows so if you have more than 50k records a workaround will need to be implemented. I recommend after 200 rounds of pagination add a branch that calls another helper flow with an API endpoint trigger then end the pagination loop. Essentially this flow will then call the pagination flow and restart the loop with the same running count. This is not included in the template. [1PaginationWithWorkflows.folder](https://devforum.okta.com/uploads/short-url/eu1MMdhn0Qzt9fAjachbIuZttNV.folder) (75.3 KB) --- _[View the full topic](https://devforum.okta.com/t/pagination-in-workflows-with-large-numbers-of-users/34611)._