frail-apricot•3mo ago
{ vf_memory } is recording a lot more than just the conversation turns
I'm trying to print the conversation history at the end of my workflow. Ultimately, this will be included in a POST request, but for now I'm just printing it in a message so I can see what it looks like.
Unfortunately, it's showing more than just the agent and user turns. It showing a lot of data related to knowledge base queries and function calls as well. See attached.
This only seems to happen after my agent finishes and the "create a workorder" path is triggered. If I print out { vf_memory } before the agent, it only contains agent/user turns and nothing else.
Is this behaviour normal? From the docs and earlier use of { vf_memory } I expected it to only contain agent/user turns.
4 Replies
You using the agent step?
frail-apricotOP•3mo ago
Yes I am. I attached a pic of the Voiceflow showing the agent if that is helpful
sorry, on my phone. yes, that is normal.
that is b/c the Agent step adds to the memory any tool call data.
try using my Transcript Function
in testing, it will show the same info you are seeing, but in production it will only show the text from the user / assistant (no tool call stuff).
@NiKo | Voiceflow @Braden (Voiceflow CEO) I do believe that vf_memory should not include any tool call info from the agent step. You should be able to filter this out.
vf_memory is different from the convo history, the agent need some info in its context, that's why memory is always more verbose.
As @W. Williams (SFT) said, using transcripts for your use case will be simpler. You can still use vf_memory (with max 100 turns) but in that case, best will be to filter only agent/user messages in a Code step before sending it to your endpoint.