# Unnecessary pagination on filtered records

**URL:** <https://community.glideapps.com/t/unnecessary-pagination-on-filtered-records/81130>\
**Category:** Report a Bug\
**Created:** [April 2, 2025, 6:33pm UTC](https://community.glideapps.com/t/unnecessary-pagination-on-filtered-records/81130 "2025-04-02T18:33:54Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Robert\_Petitto](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/robert_petitto/32/25193_2.png) [@Robert\_Petitto](https://community.glideapps.com/u/Robert_Petitto)\
**Post date:** [April 2, 2025, 6:33pm UTC](https://community.glideapps.com/t/unnecessary-pagination-on-filtered-records/81130/1 "2025-04-02T18:33:54Z")

</div>

I’ve noticed this issue a few times now. When filtering a collection (maybe just the table component? I haven’t tested…) that falls within the pagination-item count value, the pagination navigation still appears unnecessarily. For instance, in the image below, I’m displaying 11 records, so there’s no need to have to paginate through 10 pages. In fact, when clicking on any of those arrows, I get the same records.

 ![Prevailing Wage Page Count (1)](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/b/1/b1d8eb887aca83ed7e4b43510d2296b1d3ce8a3a.jpeg)

---

<div class="post-metadata">

**Author:** ![FrancoisDigico](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/francoisdigico/32/75651_2.png) [@FrancoisDigico](https://community.glideapps.com/u/FrancoisDigico)\
**Post date:** [April 2, 2025, 7:54pm UTC](https://community.glideapps.com/t/unnecessary-pagination-on-filtered-records/81130/2 "2025-04-02T19:54:08Z")

</div>

Same issue here Robert,

For me it only happens if some collection data is grouped. And exceed page limit of the container. In this example, I have more than 32 flowers, so it shows an additional pagination besides the Collection pagination limit (32).

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/1/31bc4fe2924e79a02c75d4f70f27087ed69a0d33.jpeg)  
 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/3/c/3c67552a752f1c88b6eef277c30d87a17c808c12.png)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/5/7/5773ab10392af6f71425fb0399b63ceb3664208c.png)

I guess there’s a workaround, but didn’t dig much into it yet. I would suggest to check Google Chrome Inspector Tools to debug data errors. Some happens when Glide loose track of data in tables / vs current view.

---

<div class="post-metadata">

**Author:** ![NoCodeAndy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nocodeandy/32/62530_2.png) [@NoCodeAndy](https://community.glideapps.com/u/NoCodeAndy)\
**Post date:** [April 4, 2025, 1:33pm UTC](https://community.glideapps.com/t/unnecessary-pagination-on-filtered-records/81130/3 "2025-04-04T13:33:40Z")

</div>

Flagging for the team. Thanks!

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\
**Post date:** [October 1, 2025, 1:34pm UTC](https://community.glideapps.com/t/unnecessary-pagination-on-filtered-records/81130/4 "2025-10-01T13:34:06Z")

</div>

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.