Breakpoint node makes the workflow fail if it’s placed in an inactive branch

genericknimenodes
node-execution
#1

Dear KNIMErs,
I encountered an odd case using the Breakpoint node. I’m using the Breakpoint node stopping the workflow if a certain flow variable matches predetermined value. The node works well in general but when it is inside a wrapped metanode whose branch is inactive (and so the node should not intervene at all) it brakes the flow telling that the flow variable is not available. In contrast I would expect that, if the branch where the Breakpoint is placed is inactive, it does not act at all.

I reproduced the problem in a minimal workflow attached here. There you can see that if the “selected case” is the first, the workflow fails, although the Breakpoint node should not intervene here as it is placed in the second case branch that it’s disabled.

Can anybody explain why this happen? Can you suggest a workaround?

Thank you in advance,
Gio

breakpoint_node_problem.knwf (32.6 KB)

0 Likes

#2

Hi @gcincilla,

It appears that this is a bug, thank you for reporting that!

I was able to reproduce this - the Breakpoint node for some reason stays active, even if in an otherwise inactive branch. Its output is not x’ed out, which it certainly should be.

I will open a ticket so that our developers will work on a fix. I’ll keep you posted on any news here.

Cheers,
Roland

2 Likes

#3

Very good Roland. I’m glad to know that this the reporting was useful.
Thanks for posting related news about the fix here.
Cheers,
Gio

3 Likes

#4

The fix will be available in tomorrow’s nightly build or in the next feature release (planned end of the month/early July).

2 Likes

#5

That’s a good news! Thank you very much for the fix and for updating this post.
Cheers,
Gio

1 Like