LIST isn’t a Bubble expression, could you be more precise?
If you did what I guessed earlier, its not wrong, just different to what you wanted.
There are several possible solutions, which one is useful depends on how you are doing things, and where.
Solution 1 - move the filter constraints to the search constraint.
Solution 2 - save the second filter result to a repeating group or custom state, and reference it from the merge expression.
Solution 3 - alter the second filter constraints to be appropriate for both lists.
Solution 4 - redesign so the merge isn’t needed.
LIST means a field in thing that is a list o things …anyway, I understood the behavior of expression with “merged with” and I’ve do it with your Solution 2.
Thank you a lot.