Today I accidentally realised something very unsettling. Did you guys know that the “For Each Loop” blueprint node doesn’t need it’s exec pins to be connected in order to return the array elements? Because I didn’t 
I’ve always thought that the nodes that have exec pins would need them to be connected to have a place in the execution chain since they are like actions that determine the flow of the algorithm. And considering the “for” function also manipulates the flow of the execution, it made sense to think that it’s exec pins should be connected to have a chance to be triggered. But turns out that’s not the case, because when I plug the for each loop node’s input array pin into the output array pin of something like a multi line trace node without connecting it’s exec pin, it successfully returns the array elements! Maybe it’s because there’s already a loop going on in the previous node and it’s just transfering the data but the interesting part is that… it’s the for each loop’s output pins that are plugged into the next execution pin! That’s the part which was surprising to me, because it didn’t make sense at first while thinking that it shouldn’t have returned anything at all since the loop wasn’t triggered in the first place. But I guess it can also be used as a “get” node. This kinda broke my perception on how blueprints work 
so I wonder if I share similar feelings with others who didn’t know this too until now