"Respond to chat node" doesn't detect input

Questions
1

I’ve got multiple “Respond to chat nodes”, but for one specific node the response isn’t being detected. It’s stuck at “Running for xx minutes”, even though I replied uncountable times with a specific number. This is running on my local n8n docker container.

It works for other nodes, but this specific one “Onderwerp tonen” doesn’t work 9 out of 10 times. Sometimes it randomly does work. It happens as soon as I connect “Onderwerp tonen” to “Valideer antwoord”. There are no errors in my docker container.

The odd thing is: it does always work if I activate the workflow and access the chat via the production URL. So my guts are saying the session is being lost for some reason during testmode,

This is a part of my workflow:

2

This issue might be related to session handling in test mode. Since it works consistently in production but intermittently in test mode, try clearing your browser cache or using an incognito window when testing. Also, ensure that the “Valideer antwoord” node isn’t introducing any delays or unexpected behavior that could affect the session state. If the problem persists, you might want to check the session handling logic or share the workflow JSON for a deeper look.