Kevin
Kevin
I am seeing exactly the same behavior with the redis trigger, so this might not be a MQTT only issue.
@Joffcom I would'nt call it pulled multiple times. Its almost like the redis trigger doesnt cleanup some kind of queue resulting in previous executions of the trigger running again. So...
@Joffcom The public instance is hosted in a kubernetes cluster that is publically accessible. This instance has a webhook trigger and a redis node option in the workflow (i've attached...
@Joffcom Here is some screenshots of the execution. I created this simple flow which allows me publish 1 message to redis  And here is an example of what happens...
I enabled debug logging, but no useful information there. Noticed that the Loading conversation logs happen when the sub processes start up so its not a restart causing the leak....