Chatbot - Window Buffer Memory - Error

I’m setting up a chat workflow, and I want to create some memory with the chat, but I keep getting an error indicating the value I’m receiving in the session id is not supported, but it’s what I’m getting out of the chat node.

My workflow, just getting started, so not much to it right now;

image

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Additional Information

Hi @JasonA

For a start, can you please update your n8n version and try the workflow again (also check for new node versions in the node settings tab)

If the issue persists, please share your workflow here so we can reproduce the error you’re getting.

Thanks! :pray:

Tip for sharing your workflow in the forum

Pasting your n8n workflow


Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.

```
<your workflow>
```

Make sure that you’ve removed any sensitive information from your workflow and include dummy data or pinned data as much as you can!


Hi @JasonA any luck with this issue?
I’m having the very same issue with latest version 1.72.1

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.