Hi <@U09PMQ03M99>, it seems like this is happening...
# community-help
p
Hi @Jonathan King, it seems like this is happening more often, any ideas what it might be?
j
Hi Pablo, Is the error still occurring on the 60000000001 example you mentioned before? Some more info on the data in your collections could be useful for debugging this. One reason could be that there is a parameter called
max_filter_by_candidates
that defaults to 4 unless set explicitly. This parameter determines how many possible prefix expansions are considered when filtering. For a numerical field like this with a short query like 6*, there may be prefix expansions that aren't getting considered. Could you try setting
max_filter_by_candidates=100
on your query and see if your results improve at all?