web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Automate - Building Flows
Answered

Clarification on Pagination Threshold Change

(0) ShareShare
ReportReport
Posted on by 13

Hello Anyone,

I am writing to seek clarification regarding a change I’ve encountered in Power Automate/Logic Apps. Previously, I was able to configure the pagination threshold for the Get items action to 10,000, but now the system enforces a maximum of 5,000, resulting in the error code InvalidPaginationPolicy.

Could you please explain:

  • Why the maximum threshold has been reduced from 10,000 to 5,000?

  • Whether this is a permanent platform limitation or a temporary restriction?

  • If there are recommended best practices for retrieving more than 5,000 items in a single workflow run?

Understanding the reasoning behind this change will help me adjust my workflows accordingly.


I have the same question (0)
  • Verified answer
    Michael E. Gernaey Profile Picture
    52,501 Super User 2025 Season 2 on at
    Clarification on Pagination Threshold Change
     
    This was actually changed in like 2024, so not sure why you are just now seeing errors but its been forever and a day.
     
    Its a perm change so no way but to fix your flows/logic apps as 10,000 for a page is just too much and it is. No way would I build a web app that paginates 10,000  items as who the heck wants to wait for 10,000things to load
     
    Now you are thinking but Michael DONT YOU LISTEN I said Power Automate.
     
    Yeap read it, but its the same connector and the same thing would happen in Power Apps or any other connection
     
    10K is too much, 5K is too much really but its been changed forever.
     

    If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

    Thank you!
    Sincerely, Michael Gernaey
     
     
  • AN-04030826-0 Profile Picture
    13 on at
    Clarification on Pagination Threshold Change
    Hello @Michael E. Gernaey

    Thank you for your reply and for the unique way of responding. I checked again, and actually it is possible, but only for manual flows, since they can paginate up to 10,000 items.

    Why do I need this? Because my company uses an Excel file containing past data from 2019, and it has around 59,000 rows far above the 5,000-item limit. They wanted all of that moved to SharePoint. It was a long process, but I managed to complete it, and the flow worked, although it took about two days to finish for the flow process to finish.

    Now they want to store data from Excel to SharePoint again using a recurrence trigger. The data will be kept for one year and then replaced with new data the following year. I’m still trying to figure out how to handle this in a single flow that manages two branches and processes Excel data that may exceed 5,000 rows. The stored data will also have changing data types depending on the year, since it will later be used for reminder notifications. There will be a separate dedicated flow to notify users when an item is nearing its threshold or validity date.

    Do you know any way i can do that some how with bulk data?

    Thank You!
  • Michael E. Gernaey Profile Picture
    52,501 Super User 2025 Season 2 on at
    Clarification on Pagination Threshold Change
     
    But pagination by itself doesn't really matter, not fully. And 59K is way above 10K. 10K at a time is not necessarily faster due to resource build up, caching and tear down being slower.
     
    If you want to paginate and use Do Until Loops which is how you would have to do it, Paginating by 5,000 or 10,000 at at time, understand the bigger the number the more resources it takes. I'm not even saying doing 5K at a time would be exponentially faster overall, but from a purely resource related 10K is far too much.
     
    Heck :-) Apps only do 2K max. And I get what you need to do, but you can do it in other ways aside from Power Automate and it would be way way way way way faster :-).
     
    I am glad they are going away from Excel, but you would have the same problem whether its Excel or its SharePoint or its Dataverse, you still have to paginate and when you have tons of data, its gonna be slow. From a processing perspective only, the more resources you use it within a given Cycle of a flow the more it actually uses overtime. So doing 5k at a time won't use the same as 10K at a time as the processing and cleanup happens more often.
     
    But either way you got it to work :-) and that is all that matters.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Coming soon: forum hierarchy changes

In our never-ending quest to improve we are simplifying the forum hierarchy…

Chiara Carbone – Community Spotlight

We are honored to recognize Chiara Carbone as our Community Spotlight for November…

Leaderboard > Power Automate

#1
Tomac Profile Picture

Tomac 481 Moderator

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 472 Super User 2025 Season 2

#3
Expiscornovus Profile Picture

Expiscornovus 245 Most Valuable Professional

Last 30 days Overall leaderboard