You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @xhzkp, this a peculiar behaviour but not necessarily a bug. It's happening because you're passing text to agent as: "=chatInput: {{ $json.chatInput }}\nsessionId: {{ $json.sessionId }} and have memory connected. After navigating to Executions tab, we unmount the chat component. After navigating back to the canvas, we remount it and re-render the messages from the memory buffer execution. And since the actual message that went into the buffer was chatInput: ... \n sessionId: ... that gets mapped as the user message you see in the chat
Hi @xhzkp, this a peculiar behaviour but not necessarily a bug. It's happening because you're passing text to agent as: "=chatInput: {{ $json.chatInput }}\nsessionId: {{ $json.sessionId }} and have memory connected. After navigating to Executions tab, we unmount the chat component. After navigating back to the canvas, we remount it and re-render the messages from the memory buffer execution. And since the actual message that went into the buffer was chatInput: ... \n sessionId: ... that gets mapped as the user message you see in the chat
I think this is a bug. This issue occurs whenever the Text field is custom text. Every time, I have to click the reset button and then click confirm again...
Bug Description
Watching the video makes it easier to understand what happened.
BUG3.mp4
workflow code:
To Reproduce
Expected behavior
Keep the original message text.
Operating System
n8n cloud
n8n Version
1.72.1
Node.js Version
18.16.0
Database
SQLite (default)
Execution mode
main (default)
The text was updated successfully, but these errors were encountered: