# Look Up Bug?

**URL:** https://community.glideapps.com/t/look-up-bug/86850
**Category:** Ask for Help
**Created:** [April 11, 2026, 4:36pm UTC](https://community.glideapps.com/t/look-up-bug/86850 "2026-04-11T16:36:04Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Rapex\_Technologies](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/rapex_technologies/32/94768_2.png) [@Rapex\_Technologies](https://community.glideapps.com/u/Rapex_Technologies)
#### Post date: [April 11, 2026, 4:36pm UTC](https://community.glideapps.com/t/look-up-bug/86850/1 "2026-04-11T16:36:04Z")

</div>

What will happen if lookup will exceed from 100 rows within the table where the look up column had been created?  
(This rollup is limited to 100 rows and will give incorrect results if there are more rows than that.) does someone already experience this? looking for help so will replace this type of column if this really happened to someone. Thank you

---

<div class="post-metadata">

### Author: ![Darren\_Murphy](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/darren_murphy/32/47326_2.png) [@Darren\_Murphy](https://community.glideapps.com/u/Darren_Murphy)
#### Post date: [April 12, 2026, 12:14am UTC](https://community.glideapps.com/t/look-up-bug/86850/2 "2026-04-12T00:14:22Z")

</div>

The 100 row limit only applies with Glide Big tables. It’s not a bug, it’s a constraint.