Node behavior inconsistency breaks execution – KNIME Community Hub

[Hub]

---

This is a companion discussion topic for the original entry at https://hub.knime.com/-/spaces/-/latest/~NKCbG5SFHE379eqi/

[mwiegand]

Corresponding forum posts

Inconsistent node behavior

Hi, in regards to https://forum.knime.com/t/collection-to-string-fails-if-no-collection-is-present/58756 I’d like to bring to your attention inconsistent node behaviors which break the execution of the workflow. Several nodes, despite no matching column input type is present, can be configured and executed. Like: https://hub.knime.com/knime/extensions/org.knime.features.base/latest/org.knime.time.node.convert.datetimetostring.DateTimeToStringNodeFactory [Bildschirm­foto 2023-01-08 um 10.59…

Collection to String fails if no collection is present

Good morning, I happen to recognize a few node inconsistencies amongst which also surfaced. Whilst many nodes can be configured and execute even if not corresponding column type is present, the Collection to String can be configured but fails to execute. [Bildschirm­foto 2023-01-08 um 10.49.41] Suggestion In order to ensure workflows can proceed processing (soft fail), as data might not be consistently present or compliant, I’d like to suggest to add an option make make it default behavio…