I found a small bug (but very hard to find) in a Split Node.
Let’s assume Split node has two output flows.
If first flow stops the behavior, the second flow must not be executed.
but its still be executed for current version (v1.3.5). I think its caused by for loop in Split.