I am using a switch to send call information downstream to some additional processing based on the type of call it is. In steps prior to the switch I’m attaching a value of ‘intro’, ‘scoping’ or ‘proposal’ which I then plug into to switch to route traffic. The issue I’m seeing is that the switch is passing that traffic downstream to two different paths when I pass a value of ‘scoping’ into the switch. Any idea what could be going on here?
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:
Hello, which version are you running n8n? Is this just in this workflow?
Sorry for the delayed reply. I am running v1.53.2 in the N8N cloud