Behaviour when a input change, not a bug

[lsanmartinm]

Hi!

I have a suggestion, not a platform error.
We have been using KNIME quite a bit over the last year,
and I have noticed that when an input (an Excel file, for instance) is changed, and a variable that was used later in the processing no longer exists,
the node that uses that variable randomly modifies it to another one (for example, in a rule engine).

In the interest of providing stability to a processing workflow,
it might be better if the node did not change and instead indicated as an error that the variable no longer exists.
Otherwise, it becomes complex to know where my original flow has changed,
which destabilizes the calculation.
This is especially true when adjustments are made to the input data
or re-adjustments to initial nodes.

Thanks in advance.

Best regards,

L.

[MartinDDDD]

Hey there,

moved this to Feedback & Ideas section…

Honestly the behavior you are describing sounds really weird to me… any chance you can replicate this in a very simple workflow and share?

My gut tells me that if a flow variable isn’t available anymore and a node downstream uses it the WF SHOULD FAIL and produce an error rather than randomly picking a different variable.

So it does somewhat sound like a bug to me, but would like to see it for myself…

[lsanmartinm]

Perfect, I will replicate de error in video an update

thanks for your answer

L.