"IF" node: returns both true and false paths when should be only false path

[Nadya_Motina]

Describe the problem/error/question

I got an IF node after the Telegram Trigger, which gets a telegram message and checks if it is equal to “/start” command. I expect, that if the message is “/start”, then I get the true path. And if there is any other text in the message - the false path.
But the problem is:
if a random text is received, BOTH paths are returned - true and false, one after another. How can it happen? And what should I do to avoid that?

Please share your workflow

Information on your n8n setup

• Running n8n via: n8n cloud
• Operating system: MacOS

[n8n]

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:

[gmsalomao2]

Can you try to let your workflow active and see if the executions have the same problem as the preview?

Maybe the issue only happens during editing. I’ve faced similar issues before.

[Nadya_Motina]

Yes, I checked it active, in production mode, and the problem remains

[liam]

Can you please provide some sample trigger data so I can try to recreate the issue?

[Nadya_Motina]

Yes, sure

[
  {
    "update_id": 675728302,
    "message": {
      "message_id": 152,
      "from": {
        "id": 191068700,
        "is_bot": false,
        "first_name": "Nadya",
        "last_name": "Motina",
        "username": "thatdau",
        "language_code": "ru",
        "is_premium": true
      },
      "chat": {
        "id": 191068700,
        "first_name": "Nadya",
        "last_name": "Motina",
        "username": "thatdau",
        "type": "private"
      },
      "date": 1714225733,
      "text": "aaa"
    }
  }
]

[liam]

Found your issue!

You have always output data enabled. That should be turned off

[Nadya_Motina]

@liam Thank you so much!!
I didn’t even know about that parameter.

[liam]

it can be useful sometimes!

it is off by default, so you probably turned it on by accident somehow