Why doesn't the chat node use the session ID I see in the console?

When I test a workflow that starts with the chat, I frequently need to start a new session from zero. But when I reset the session, the chat uses the old session ID. It uses a new ID only when I reload the page.

Why?

1 Like

Yes, indeed — I can confirm the same behavior..

1 Like

I’m experiencing the same behavior. When I reset the session, the chat still keeps using the old session ID instead of generating a new one. The only way to actually start with a new session ID is by reloading the entire page. It seems like the “reset” action doesn’t fully reinitialize the session context unless the page is refreshed.

1 Like

I am facing the same issue as well. The ‘reset’ session button clears the chat panel and generates a new session id but it doesn’t get passed further down to the next node. It still reuses the old session id. Any workarounds are appreciated (except refreshing the page)

I am experiencing the same issue. only full refresh fixes it.

I’ve duplicated this issue on versions 1.114.4 & 1.118.1 self-hosted

Glad we’re all confirming it’s a bug. Does anyone know if a fix is being looked at?

Probably sadly not. Bugs have to be reported via GitHub: GitHub · Where software is built

Please post the Bug there. The team can then have a look. Thanks!