I’m trying to add a connection between two existing nodes in a workflow. When I do, I get the following popup: (Workflow Coach is off.)
If I add a new node, the connection works.
If I add a new node, the connection works.
Hi @rfeigel , I don’t think this is anything to worry about, (unless I’m misunderstanding what you are saying 
)
In Modern UI if you drag out from a particular port (e.g. flow variable port in this case), the pop up “search compatible nodes” dialog is simply showing nodes that are compatible with the port you’ve dragged from, (which being a flow port is all of them, I think! But if I’d dragged from a table port, it wouldn’t show any “variable-only” nodes) I think that’s all it means.
The “search compatible nodes” label is simply a label for the search field where you can type the node name you are looking for.
I quite like this functionality but it isn’t without it’s flaws.
For example dragging a case switch configured for variable ports to attach a case switch end …
… results in an incorrect connection. 
I can understand why, but I would like to see the “intelligence” of the operation improved, so it automatically applies the “obvious” connections:
Thanks @takbb. The real problem is that the connector won’t connect. If I drag it to the connection point on the second node it disappears when i lift the mouse.
Ah, sorry @rfiegel, I slightly misunderstood.
Which version of KNIME is it? Does it happen all the time?
I’ve not really been able to simulate exactly what you’re seeing. The closest I’ve got to it is by artificially placing the output data-flow line from the Timer Info backwards across the node so that its presence “obscures” the input flow port and KNIME doesn’t always then see it as a “drop point”
But I haven’t managed to do it without putting the output flow line right across the input flow port, so it isn’t exactly what you’re seeing. In your first screenshot though, you do appear have a data flow across heading backwards from your Timer Info node data output port, so it may be related and I’m guessing KNIME is getting slightly confused by it, or something that it thinks is obscuring the port. Possibly a small visual “glitch” ?.
If you adjust your Timer Info node’s position, (or the data flow coming out of it) does it stop this issue occurring?
@takbb Thanks for all your trouble. I’ve tried moving the offending nodes in a variety of positions. Nothing seems to help. Its the only time I’ve had this problem so its not a big deal. Apparently the original workflow configuration hard wired something which is causing the problem. I’ve tried KAP 5.5.1 and 5.6.1.
1 Like