OR Filter + Max Load shows global messages instead of filtered results

[Yuki.O]

OR condition breaks when using contains Logged In User on a User list (Adalo filter bug?)

Hey @Yuki.O, You’re very welcome, I’m glad this issue has been solved. You can check also some tips on database structuring/relationships (like filtering, many-to-many, or performance), on this post: A Practical Approach to Structuring Collections in Adalo Good luck with the app!

Issue with OR filter + Max Load (messages get hidden)

I’m using an OR filter to show messages related to the logged-in user.

Condition A

• Logged-in user is the sender

Condition B

• Logged-in user is included in Question-receivers (receiving the message)

Each condition works correctly on its own.

However, when I apply Max Load = 17 to this OR-filtered list, the behavior is incorrect.

What actually happens

• The list shows the latest 17 messages from the entire Messages collection

• Messages that should match Condition A or B but are older than those 17 are not shown

• As a result, valid messages for the logged-in user are hidden

What I expect

• For Condition A: show up to 17 messages sent by the logged-in user

• For Condition B: show up to 17 messages received by the logged-in user

• In other words, Max Load should apply after the OR filter, not to the whole collection

This makes it impossible to use Max Load safely with this OR filter, because relevant messages get buried as more messages are created globally.

Is this a known limitation or a bug with OR filters + contains (User list) + Max Load?

[Dilon]

Hi @Yuki.O,

@Yuki.O

What I expect

• For Condition A: show up to 17 messages sent by the logged-in user
• For Condition B: show up to 17 messages received by the logged-in user

From what I see, you would need two lists in your case instead an OR filter to retrieve 17 records in both ways along with a sorting filter.

Thank you and have a great day!

[Ali-Bazzi]

Hey @Yuki.O,

The OR filter + Max Load pulling global records instead of filtered ones is a known limitation, Max Load can apply before the OR logic fully evaluates.

The reliable native workaround:

Use two separate lists:

• List 1: Filter where sender = Logged In User, sort by Created date descending, Max Load 17

• List 2: Filter where Question-receivers contains Logged In User, sort by Created date descending, Max Load 17

Place them in a vertical group (List 1 above List 2 for newest first overall).

This shows the newest 17 from each condition, combined sorted, no bugs, loads fast.