MemoryStoreManager.invoke() runs the same search twice

[jiangwu25]

When I call MemoryStoreManager.invoke() without a query_model, it runs the same search twice.

I tested this on main with one message and query_limit=5:

• The first search uses a limit of 10.
• The second search uses a limit of 5.
• The code only keeps the result from the second search.

The two searches are here.

Can I remove the first search and add a test for this case?

[AbhishekRP2002]

Hi @JiangLLM , thanks for reporting this and pointing to the relevant code. I reproduced the duplicate search locally and pushed a small fix with a regression test: #190

The patch removes the unused first search while retaining the executor-backed search that respects query_limit. Please let me know if you’re already working on this—I’m happy to coordinate and avoid duplicating effort.

[samvallad33]

MemoryStoreManager invoke running the same search twice doubles latency and can race two extractions into conflicting writes. Duplicate searches also muddy threshold decisions when one hit set differs. Are you collapsing invoke into a single search path with shared result caching before extraction commits?