After debugging, I found that the last sorting field, is optional. If there isn't a match with that field, by defaut we assign it a super low score, and as results fill up, they will always be bumped down, removing them from the end result.For that, you will need to assign a behavior for the missing values. We have some docs for it: https://typesense.org/docs/28.0/api/search.html#sorting-null-empty-or-missing-values Adding this:

"sort_by": "_vector_distance:asc,genericFlField2(missing_values:last):asc",

Will return all 200 results