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.
Thanks all.
Alas the problem is now resolved.
That wasn't the ACTUAL problem. I only noticed it while looking for the REAL problem.
Since it isn't ....... resolvable ....... with information a hand and all that: I'll mark it as solved.
I think I tried that. No change.
I may be wrong. But there were a few redeploys happened as I was adding the new nodes for testing.
HUGE UPDATE
(If anyone cares)
I just realised an important factor in why the debug nodes weren't showing their output.
(Want to guess?)
(Shame I can't leave spoiler space here)
A few weeks back I was chasing something and had to go from my default this flow to selected nodes.
And never reset it back to this flow.
So only the selected nodes would appear in the debug window.
TRAP FOR NEW PLAYERS!
No worries, happens to the best! 
I ran into that trap myself a few times.
oh man thats such a killer because you'd never think to check that setting when everything else looks normal. bet that was hours of staring at the change node wondering what broke
