# Complex Worklfows and Filtering Limits

**URL:** <https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271>\
**Category:** Ask for Help\
**Created:** [February 22, 2025, 4:42pm UTC](https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271 "2025-02-22T16:42:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kristo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kristo/32/85481_2.png) [@Kristo](https://community.glideapps.com/u/Kristo)\
**Post date:** [February 22, 2025, 4:42pm UTC](https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271/1 "2025-02-22T16:42:17Z")

</div>

Hey there Gliders,

i am currently trying to build Glide App that helps my Team to track Expenses against their current Projects.

User and Projects are N:N whereas Projects to Expenses are 1:N Relations.  
The challenge here is that Receipts and Projects are multi currency. I got the conversion covered via API call when they are created. Easy bit …

But now I am just covering for the case when the Admin requires to change the Project Currency when already Receipts are linked. Therefore i would need to check which Receipts need a new conversion rate (a.k.a new API call)

I think i got that sorted as well with triggering a Webhook on UserAction that will pass on a JSON and trigger a Loop Flow.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/8/c/8c619defe9dfd2f7b7d357e87f20cf5b9caf5896.png)

What i am trying to understand is how the “Filter Function works” as it is limited to 1000 rows. the question here is :  
How do I correctly filter the data to avoid hitting that limit. As i have in the same table many receipts and i dont really need the loop to run through all of the receipts only the ones that were associated with the Project. hence the Filter.

I figured two ways to set it up first one is by adding a “computed Query” prefiltering the Table and the using that data within the Loop Flow.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/e/e/eea87fabdc374bbd5a9753b5d484692074611839.png)

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/6/3/63c387b8b85181f2296edb031622a65719949a9f.png)

Is the “computed Query” Limited by the amount of Rows in source table it is querying ? and what’s the limit the Result it can contain ? On the latter question I am sure i wont exceed 200 Receipts per Project, so i presume that should be safe then!

But i also saw that you can set a filter directly in the Loop settings.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/d/a/dad7af38309d149f6d1ddeb8699530d3bf2c262d.png)

Whats the difference in either scenario ?

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [February 23, 2025, 1:57am UTC](https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271/2 "2025-02-23T01:57:21Z")

</div>

> [@Kristo](#):
>
> Is the “computed Query” Limited by the amount of Rows in source table it is querying ?

I’m not quite sure if there’s a limit at all on the rows that are in consideration, I think the advice I got is not to loop through more than 1000 rows.

---

<div class="post-metadata">

**Author:** ![Kristo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/kristo/32/85481_2.png) [@Kristo](https://community.glideapps.com/u/Kristo)\
**Post date:** [February 24, 2025, 7:17am UTC](https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271/3 "2025-02-24T07:17:57Z")

</div>

Great thanks for the reply. I doubt that i will loop through more than 1000.  
hence i wanted to pre-filter the data before running the loop.

is there a difference if i set the Filter directly in the loop or if i do a “computed query” with the filter applied before using that data in the loop.

---

<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:** [February 24, 2025, 7:26am UTC](https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271/4 "2025-02-24T07:26:10Z")

</div>

> [@Kristo](#):
>
> is there a difference if i set the Filter directly in the loop or if i do a “computed query” with the filter applied before using that data in the loop.

No difference that I am aware of. One reason why you might use a computed query in preference is that you might use it for other purposes within the workflow.

---

<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:** [March 3, 2025, 7:26am UTC](https://community.glideapps.com/t/complex-worklfows-and-filtering-limits/80271/5 "2025-03-03T07:26:33Z")

</div>

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