I would still consider it a bug, or at least very, very unexpected behaviour.
1. the error-out of the loop does not trigger automatic error handling. I didn't check the error terminal, because I expected it to pop up a message if an error occured.
2. the error message is "Timed structure aborted or attempted to execute another iteration of the following aborted Timed Loop." Btw. in the german version of the error text the "Timed structure aborted or" is not mentioned, so I don't know if aborting a loop from the outside itself is already considered an error. If it isn't then where is the additional try of executing the loop coming from? The iteration itself obviously does not happen, as the counter, the output of the FB node and the single cluster show.
3. In any case I would expect the loop counter to match the last index of the array (i. e. i+1 elements in the array). If not that, than to be consistent at least the tunnel of the single cluster would have to revert to it's default value.
4. If the supposed way of stopping a timed loop is by handling the "aborted"-case inside the loop, then using the conditional terminal should be mandatory (as it is with normal while loops).
