I don’t know why we are evening talking about this … nested looping has been a standard in every programming language (which N8N is trying to replace) going back to the beginning of time. If nested looping is not supported, you should not be able to create it in the interface. It should check for nested looping and throw up an error. I have created two workflows that were nested loops before figuring out that it was not supported. 