Well, I would say that Sequence nodes do in fact fire the second wire after the first one is through.
Otherwise a lot of my own logic wouldn’t work and the Sequence node itself would be useless.
Now, what could lead to a second half of the SAME code not working if called together with the first part?
Hm, let’s see, is there maybe something that should be unique? Something that is even called “unique”?
Maybe something like an Instance Name that you are setting to “INDEX1xINDEX2”?
Na jokes aside, do you maybe use the same names for the Instances? I see you combine the Loop indices
with an “x” in the Append node. Is the lower half of the code using the same Loop indices and maybe just not creating the instance
due to reusing the same name?
Could be wrong, but testing on my end has indicated that Sequence nodes only ensure that the very first function/event/node in the execution chain on a higher (position) branch get called before the very first function/event/node in the execution chain on lower (position) branches. The order they’re called in is preserved, and can be relied on. However, there is either no delay, or a very short delay, and the node does not wait for it’s top branch to finish before proceeding to the next branch.
Order (of being called) is preserved. But if your top branch takes too long and your bottom branch relies on data from the top branch’s execution- things can go wrong.
That being said, I totally missed the actual error .