Others

How to Fix Power Automate Scheduled Flow Limited to 5000 Rows

Chanuka Geekiyanage Oct 1, 2026 868 views

Question details

Users need a way to process more than 5,000 rows in a scheduled flow without triggering a pagination limit error.

Fixing the Power Automate Scheduled Flow 5,000 Row Pagination Limit

Product: Power Automate
Device & OS: not provided
Scenario: Attempting to retrieve or paginate large datasets (e.g., 15,000 rows) automatically via a scheduled Power Automate workflow.
Observed behavior: Saving the flow returns an error stating that the scheduled flow limit is 5,000 rows, preventing any pagination value above this threshold.

Before you start

Verify your specific Power Automate licensing tier and the limitations of the specific connector you are using, as maximum payload limits vary between standard and premium connectors.

Solution 1Recommended

Apply OData Filter Queries to Reduce Data Payload

Filter out unnecessary records directly at the data source so the flow only retrieves the exact data needed, keeping the total under 5,000 rows.

Instead of pulling an entire database into Power Automate and filtering it later, OData queries instruct the server to only send back matching records. This is the most efficient way to prevent pagination errors.

Open Action Settings

Select the data retrieval action in your flow, such as 'List rows present in a table' or 'Get items'.

Locate Filter Query

Click on 'Show advanced options' within the action card to reveal additional settings, including the 'Filter Query' field.

Input OData Syntax

Enter a valid OData query (for example, Status eq 'Active' or Created gt '2023-01-01') to restrict the pulled records to a subset smaller than 5,000 rows.

Apply OData Filter Queries to Reduce Data Payload

Performance Boost: Using OData filters not only circumvents the row limit but also significantly speeds up your flow's execution time.

Solution 2

Process Records in Batches Using a Do-Until Loop

Use a looping structure to retrieve and process data in manageable chunks of 5,000 rows or fewer.

Solution 3

Consult the Power Automate Community for Licensing Workarounds

Reach out to specialists to confirm if upgrading your plan or using a custom connector alters the strict limits.

Free Microsoft Office alternative

Efficiently Analyze Large Datasets with WPS Office

When automated workflows like Power Automate hit rigid limits, managing the exported data doesn't have to be a struggle. WPS Office provides a robust, lightweight environment to handle, filter, and analyze massive datasets effortlessly.

1. Download the Software: Visit the official WPS Office website and download the free installer for your operating system.
2. Install WPS Office: Run the downloaded file and follow the on-screen instructions to complete the quick installation process.
3. Analyze Your Data: Open WPS Spreadsheet to import your large .csv or .xlsx exports and utilize powerful built-in tools like PivotTables and advanced filtering.

Fully compatible with Microsoft Excel formats (.xlsx, .csv) generated by standard data flows.Handles heavy datasets with thousands of rows without the performance lag of browser-based tools.Free and lightweight, helping you bypass expensive premium enterprise licensing.Familiar spreadsheet interface ensures zero learning curve for seamless data migration.

microsoft office alternative - wps office

Frequently Asked Questions

Why do I get a pagination error when I enter 15,000 rows in Power Automate?

Scheduled flows and many standard connectors in Power Automate have a hard limit of 5,000 rows for pagination to protect server resources. Attempting to save a flow with a value higher than this threshold triggers a system error.

Does upgrading to a Power Automate Premium plan fix the 5,000 row limit?

It depends on the connector. While a premium plan increases overall API request limits and allows access to premium connectors that may have higher thresholds (sometimes up to 100,000 rows), scheduled flows themselves may still enforce strict batch sizes depending on the data source.

What is the most efficient way to extract large amounts of data without hitting this limit?

The most efficient method is using OData Filter Queries to filter data at the source before it reaches Power Automate. If you truly need all the data, implementing a Do-Until loop with 'Skip Token' or 'Skip Count' allows you to pull the data in acceptable batches of 5,000.

Office Quick Solutions