Debug node change when no change made

Core Development
1

Hi There,

Can someone confirm this or is it just me but does a debug node cause an unnecessary change?

What happens is that I create a new debug node, save the flow, open the edit panel for the debug node, make no change, close the debug edit panel and the flow has changed or rather the deploy button tells me something changed. I save the changes and then open the edit panel for the debug node, make no change again but this time the flow isn't changed.

Is this just my installation of Node-RED? Tested with 4.0.5.

debug-node-change

Is this just me or does it happen for others too?

1 Like
2

Same on 4.0.5 and 4.1.

Related to node.complete and node.targetType changing:

Capture dā€™eĢcran 2025-08-19 aĢ€ 20.02.57
Capture dā€™eĢcran 2025-08-19 aĢ€ 20.02.571216Ɨ208 33.6 KB

1 Like
3

Thanks for checking and saving my sanity!

I also suspected, complete & targetType - I changed them here to:

-            complete: {value:"false", required:true},
-            targetType: {value:undefined},
+            complete: {value:"payload", required:true},
+            targetType: {value:"msg"},

since that's the default ....

4

Same for me. Only happens on first adding a debug node. Then deploy, open the panel, click done. Doesn't happen again.

1 Like
5

Yep but with each and every debug node added! So it be kinda weird...