Join node remembering more than it should

Can someone see if this problem with the Join node is just me please? Be careful not to do anything out of order as the problem has a habit of going away and I am not sure what makes it go.

  1. Import the flow below and deploy it.
  2. Click the Inject node A:timestamp msg.full:true
  3. Note in the debug node that the message has msg.full present.
  4. Click the Inject node A:timestamp No msg.full
  5. Note that the message still has msg.true present, which it should not.

Having said that the problem sometimes clears itself, I now find that I cannot make it clear.

[Edit] node-red 3.0.2, nodejs 18.13.0

[More edits] Here is the flow that I didn't include.

[{"id":"bb68bb3693e0d1f1","type":"inject","z":"bdd7be38.d3b55","name":"A:timestamp  No msg.full","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"A","payload":"","payloadType":"date","x":210,"y":3200,"wires":[["f9e9e10d41b65ca1"]]},{"id":"30e24e64b1b57f52","type":"inject","z":"bdd7be38.d3b55","name":"","props":[{"p":"payload"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"B","payload":"","payloadType":"date","x":230,"y":3340,"wires":[["f9e9e10d41b65ca1"]]},{"id":"a99c557ae2cf9bfc","type":"inject","z":"bdd7be38.d3b55","name":"A:timestamp   msg.full:true","props":[{"p":"payload"},{"p":"topic","vt":"str"},{"p":"full","v":"true","vt":"bool"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"A","payload":"","payloadType":"date","x":170,"y":3260,"wires":[["f9e9e10d41b65ca1"]]},{"id":"47ac7e6620607619","type":"debug","z":"bdd7be38.d3b55","name":"debug 70","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":700,"y":3260,"wires":[]},{"id":"d4a479ac4ee76c68","type":"join","z":"bdd7be38.d3b55","name":"","mode":"custom","build":"object","property":"payload","propertyType":"msg","key":"topic","joiner":"\\n","joinerType":"str","accumulate":true,"timeout":"","count":"1","reduceRight":false,"reduceExp":"","reduceInit":"","reduceInitType":"","reduceFixup":"","x":550,"y":3260,"wires":[["47ac7e6620607619"]]},{"id":"f9e9e10d41b65ca1","type":"junction","z":"bdd7be38.d3b55","x":400,"y":3260,"wires":[["d4a479ac4ee76c68"]]}]

There is no flow below?

Aargh! I am going do-lally.

I have added it.

Or should that be doolally?

I can't possibly comment ! :upside_down_face:

As you say, msg.full is still there.

I tested msg.payload {"name" "Cinderella", "hero": "Prince Charming"} in the first msg
and {"name" : "Aladdin", "password": "Abracadabra"} in the second.
Fortunately msg.payload.hero was not retained!

(The pantomime season is behind me)

OK, thanks. I will wait a bit in case @knolleary tells us it is already fixed in git before submitting an issue. It is a fairly serious issue, it took me quite a while to work out what was going on.

I don't recall an issues being raised related to the join node. Suggest you get it raised so it can be looked at.

Sorry, not paying attention.

Oh no it isn't ...

1 Like

Issue raised