Hi,
when testing something I noticed that incompatible node configurations only soft-error out. Making them catchable would help to improve workflow automation.
Just as a side node, having invalid configuration hard-fail would auto-reset the execution and be counter-productive.
WARN Row Filter 3:18 Errors loading flow variables into node : Errors overwriting node settings with flow variables: Can't evaluate variable "Row0" as xstring expression, it is a STRINGARRAY (""Row0" (STRINGARRAY: [semicolon;semicolon, backslash\bakslash, quotes"quotes])"
PS: raising this as both bug and a feature request as it’s unclear into which category it falls.
Best
Mike