MQTT Topic Event triggers Random MQTT Triggers in one Workflow

[ToRoCu]

Bug Description

MQTT topic event triggers random MQTT trigger nodes in a workflow, always a different one if there are several in a workflow.
The incorrectly triggered node then also receives the data of the MQTT event.
The whole thing only happens if a workflow is activated.
In short, one MQTT topic alternately triggers all MQTT trigger nodes in a workflow.

To Reproduce

1. create 2 or more MQTT trigger nodes and assign them different topics e.g. test/one, test/two and so on
2. link these with an event e.g. an MQTT Puplish in another topic like test/msg and assign different messages e.g. test/msg = one_isTriggered or two_isTriggered
3. switch the workflow to active
4. now puplish into one of the topics e.g. test/two, 3-4 times if you like
5. now you will see that when you puplish in test/two, the trigger of test/one is also triggered

Here you can see that test/one has been published but trigger three has been triggered but the information from test/one has been transferred.
(Screenshot of the past executions)

Expected behavior

That only the trigger node that has set the corresponding topic is triggered.

Operating System

Docker

n8n Version

1.72.1

Node.js Version

Container Integrated

Database

SQLite (default)

Execution mode

main (default)

[Joffcom]

Hey @ToRoCu,

We have created an internal ticket to look into this which we will be tracking as "N8N-8055"