I'm confused.
I seem to be losing messages through this change node.
Global context PROOF OF LIFE here.
Used here.
Message comes in.
(Green) you can see the message.
change node as shown.
Nothing coming out.
(Red)
Confused.
try using the message tracing of the introspection package - then you'll see the true path of the message.
looking at your screenshot, it's probably something to do with this non-connected output:
but that's all I can by looking at three screenshots ....
Thanks.
But all I did between "then and now" is add a second trigger node to show the message leaving, added an extra inject node to inject a test message.
I pressed the inject node, and nothing was seen in the debug nodes.
The two trigger nodes both triggered showing the message/s were leaving.
So I deleted the two suspect debug nodes and replaced them.
Now all working.
Kinda worrying.
The non connected output of the switch node is just a filter for the msg.topic
That particular topic isn't tested.
I have sometimes had Debug Nodes stop publishing messages after updating NR.
It is possible that the state presented in the editor is getting inconsistent with the actual state in the runtime.
That can happen when debug nodes get activated/deactivated and deployed from another editor session.
Simply disable -> enable -> deploy fixed it for me most of the time.
If it is that then a browser page refresh should sort it.
