Hi everyone, I am working on a workflow and I am facing dysfunctionality for using try-catch error nodes in an inactive port. To clarify my explanation, I have a workflow with empty table switches and within each of them I have one component with multiple try-catch error nodes in it. As a normal behavior when the component is in the inactive port, I expect the component should be inactivated and the end if node should choose one of the ports and be run after it; but when I run the “End if” node it is not going to run and my workflow does not proceed anymore. [abnormal] [try-catch-abnormal] It is so strange because it shouldn’t act like this. Normal behavior: [try-catch-normal] Although I can not share the exact workflow but this is an example for the workflow structure that I am working on, I have tried to face the same error in this workflow but I could not. Try-catch.knwf (45.1 KB) So, if anyone can help me with this error I would be appreciated. Mona

Hi @monaJZ , If you have any Breakpoint node in the inactive branch and they are using flow variables which are generated in the branch, Make sure you provide a fake variable before the switch node passed to the branch. @ScottF I think this issue is unexpected: When we use a Breakpoint node in an inactive branch and we use a flow variable in it which is generated in the branch, the Breakpoint node still looks for the variable and if it doesn’t find it, the branch would fail (actually the switch will not be closed). I think the Breakpoint node shouldn’t look for variables if it’s in an inactive branch. :blush:

Try-catch abnormal behavior

KNIME Analytics Platform

qqilihq July 5, 2021, 10:30am 2

Do you see any error message? Could this be the issue described here?

2 Likes