Hello,
Thanks for reporting this issue, we are looking into a fix for this. In your example, you are switching a 2in/4out with another algorithm that has 2in/2out, and I believe that is what causes the unexpected routing to happen. If all of your algorithms are 2in/2out, for example, this should not happen.
I’ll let you know when we have a better idea about a fix for this. Sorry for the inconvenience.
