extracted_memories

[vanessa1412]

Hello, and first of all, congratulations on the great work — it has been extremely useful. I would like to clarify a question regarding the mem0 API. When I send the full conversation to mem0, the code finishes running normally, but mem0 itself places the processing in a queue. When I attempt to access extracted_memories, I receive the message: "Memory processing has been queued for background execution". Is there a way to force synchronous processing or to check the status of the background queue? Thank you in advance!

[hush-cd]

Hi, thanks for your kind words and for raising this question 🙂

During our initial testing, the mem0 API behaved synchronously, so the current implementation in this repository assumes a synchronous add call and directly reads extracted_memories from the response.

However, as mentioned in Mem0’s recent update, the Memory Addition API is changing its default behavior: starting November 8, 2025, async_mode will default to True. Under this mode, memory extraction is queued for background processing, which is why you’re seeing the message “Memory processing has been queued for background execution”.

At the moment, this repository has not yet been updated to handle the new async behavior, such as polling for status or explicitly disabling async mode. If you need synchronous processing or queue status checks, you’ll need to adjust the API call according to Mem0’s latest documentation (e.g. explicitly setting async_mode=False, or implementing a status-check flow if supported).

Thanks again for the feedback — we’ll keep this change in mind for future updates.