Reason is clear.
Fuzzy search logic on backend assumes each aspect property has parent aspect and looks for it.
However there are some kind of zombie properties in production db.
Why such properties appeared is separate question for invesgation.
I guess that they are remainings from some old bugs fixed a while ago. (Otherwise similar issue would be present in stage2 environment which is not case)
Solution is following:
Throw away results with zombie properties
Make fuxxy search more fault tolerant. In particular, handle exceptions for each of subquery to avoid logic "exception in any of subqueries leads to total fault".
Reason is clear. Fuzzy search logic on backend assumes each aspect property has parent aspect and looks for it. However there are some kind of zombie properties in production db. Why such properties appeared is separate question for invesgation. I guess that they are remainings from some old bugs fixed a while ago. (Otherwise similar issue would be present in stage2 environment which is not case)
Solution is following: