Simple bug to reproduce, un comment the the onFindOPGetValues() function, and try something that would produce an error, like getting a parameter value that doesn’t exist on an op.
Instead of producing a python error / red X on the node, it just quits what it’s doing making it seem like maybe there is a problem with the configuration of the node.
I guess not so much a bug as a lack of visibility into why it doesn’t produce the expected results.
opFindDat_NoReportedErrorBug.1.toe (3.9 KB)