Messages are stored in Honcho, a background process called the
Deriver is
triggered to reason about the conversation and generate insights.
The Deriver is an asynchronous process and, depending on load may not immediately
generated insights for the latest message you’ve sent. To help with this, Honcho
provides several utilities to check the status of the Deriver.
Message is sent it will generate several tasks. These could
be tasks such as generating insights, cleaning up a representation, summarizing
a conversation etc. These tasks are defined based on who is sending the
message, what Session the message is in, and potentially who is observing the
message. We call the combination of these parameters a work_unit
This has a few different implications.
- tasks within the same work_unit are processed sequentially, but multiple work_units will be processed in parallel
- If local representations are turned in a Session then a
Messagewill generate an additional work unit for everyPeerthat hasobserve_others=True
get_deriver_status and poll_deriver_status methods can take additional
parameters to scope the status to a specific work unit
Session objects in each of the SDKs.
Below are the function signatures for the session level deriver status method