# Two nodes apparently connected by two wires (bug?)

**URL:** https://discourse.nodered.org/t/two-nodes-apparently-connected-by-two-wires-bug/58553
**Category:** General
**Created:** [17 February 2022 19:16 UTC](https://discourse.nodered.org/t/two-nodes-apparently-connected-by-two-wires-bug/58553 "2022-02-17T19:16:01Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![AndrewRoy](https://avatars.discourse-cdn.com/v4/letter/a/f08c70/32.png) [@AndrewRoy](https://discourse.nodered.org/u/AndrewRoy)
#### Post date: [17 February 2022 19:16 UTC](https://discourse.nodered.org/t/two-nodes-apparently-connected-by-two-wires-bug/58553/1 "2022-02-17T19:16:01Z")

</div>

Running v2.2.0 I apparently have two nodes that are connected by two wires.

The output of node 1 was wired to flow into the input of node 2. But node 2 seemed to be getting the message twice. After some debugging, I could tell that their were two wires connecint the two nodes. Looking at the flows.json I discovered this (note the dpulicate wires):

{  
"id": "2915cc26.3bb194",  
"type": "function",  
"z": "0dce15414a6fc61c",  
"g": "e28f6ea.8b8e59",  
"name": "is commandSendDefinitions Absent?",  
"func": "if ( global.get('commandSendDefinitions') === undefined )\n return msg;\nelse\n return null;",  
"outputs": 1,  
"noerr": 0,  
"x": 670,  
"y": 120,  
"wires": [  
[  
"bf7bf35a.df4f9",  
"bf7bf35a.df4f9"  
]  
]  
},

I actually found it by placing a function node over the wire in the UI to do some debugging and the UI automatically wires the new funciton node in. I then moved the function node but there was still a wire connecting the two nodes.

You can see the process below:

1. The UI
2. Dropping the funciton node
3. The UI wires the new node in
4. Move the function node to see that there is still a wire there.
5. While not included in the graphic, I moved the other nodes around to make sure that the extra wire was between the two offending nodes. Seeing this brought me to looking at the flows.json and seeing the duplicate wire entry.

 ![Dup-Wires](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/d/b/db1b4e757a07b3f0363c46f66ad45fd72ea25cf8.jpeg)

If I can be of any further help, please let me know.

Thank you.

---

<div class="post-metadata">

### Author: ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)
#### Post date: [17 February 2022 19:42 UTC](https://discourse.nodered.org/t/two-nodes-apparently-connected-by-two-wires-bug/58553/2 "2022-02-17T19:42:17Z")

</div>

Can you recreate it at will? If so, what are the steps?

---

<div class="post-metadata">

### Author: ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)
#### Post date: [17 February 2022 19:52 UTC](https://discourse.nodered.org/t/two-nodes-apparently-connected-by-two-wires-bug/58553/3 "2022-02-17T19:52:38Z")

</div>

This was fixed in the 2.2.1 release

> [@tada Node-RED 2.2.1 released](https://discourse.nodered.org/t/node-red-2-2-1-released/58392):
>
> Node-RED 2.2.1 is now available. This fixes an issue that could lead to multiple wires being added when undoing a delete. As well as fixing the path that could lead to that, it will also actively filter out any duplicate wires in the flow just in case your flow has been affected and you've not noticed. There are a few other useful fixes in there as well - full details on GitHub

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [18 April 2022 19:53 UTC](https://discourse.nodered.org/t/two-nodes-apparently-connected-by-two-wires-bug/58553/4 "2022-04-18T19:53:05Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
