We mostly keep our channels separate and don't mix it. But for the ones that we do, we don't start multiple paths from the Start node. We would keep the path linear.

I agree that it seems limited. I've leveraged other tools with similar UI that allows you to build what you built and encourage it. Hopefully Iterable follows suite.

There's nothing wrong with your setup, but I would imagine that as your company scales and the audience size grows, this type of unsupported setup might put a process strain on Iterable and I wouldn't be surprised to see delays and/or drops.

Lauren Cory, thanks so much for the question and Raj Singh, thanks so much for weighing in! We don't officially support this, as to Raj's point, it can cause a lot of strain on the system to run these paths in parallel. Is it critical that the paths happen simultaneously, or can they happen more sequentially? It seems as if these paths could be condensed into one and you would still be able to accomplish what you're trying to achieve. Not sure if I might be missing something. I can definitely see the value in being able to more easily see the different tracks as separate paths...