Id names several nodes or connections

Two nodes, or two connections, carry the same id. A change addressed to that id would land on both, and a run would keep only one of them, so the change is refused. The canvas gives every node and connection its own id, so this arises when an agent or tool writes the workflow or when a workflow is imported from a file.

What to do

Give each node and each connection its own id, and point each connection at the node meant. The message lists where the id appears.

Where it comes from

Checked before every run, for any node. It is one of the messages checks before a run.