Pagination

(0) Share

Report

Posted on by CU24060538-0

Hello,

I have a Postgres get rows action in my flow that retrieve data from the table. Without the pagination, it only bring 512 rows even though we have 751.

Then I tried enabling the pagination and now it's retrieving 751 rows but they are duplicates.
I have checked and verified my postgresql table and there are no duplicates there.

I tried connecting the same table to powerbi and powerapps and there are no duplicates and data match with postgresql table.

But in power automate it's not matching and giving duplicates when pagination is enabled.

Please suggest any alternative or any solution.

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Vish WR 3,748 on at

Like
a
(1)

Report
Copy link

Link copied!

@CU24060538-0

It sounds like a pagination-related issue. By default, the PostgreSQL “Get rows” action returns a limited number of records, which explains the 512 rows. When pagination is enabled, try adding an explicit sort on a unique column (such as the primary key) to ensure rows are returned in a consistent order across pages. Without a stable sort order, duplicate records can appear even when the source table contains no duplicates.

vishnu

wrvishnu.com | LinkedIn

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @wrvishnu for follow-ups.

Was this reply helpful? Yes No
Suggested answer

chiaraalina 2,425 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CU24060538-0

Do you use Order By parameter?

I see Order By is only recommended if pagitnation is not used: PostgreSQL - Connectors | Microsoft Learn

This means:
Page 1: ORDER BY works correctly → retrieves rows 1-512
Page 2: ORDER BY is ignored → retrieves an arbitrary set of 239 rows (751 - 512)
Result: Some rows from Page 1 may reappear in Page 2

Was this reply helpful? Yes No
Suggested answer

MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@CU24060538-0,

This is a known behavior with Power Automate + PostgreSQL connector — when pagination is enabled, duplicates usually happen due to missing deterministic ordering in the query.

If your query (or Get Rows action) does NOT have a stable ORDER BY, then:

Iteration 1 will retrieve some set of rows and Iteration 2 may re-read overlapping rows which may result redundancy in the data

Add Order By in your "Get rows" action

Note: Consider the Unique Column or Primary Key Column for Order By

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No