I think people are missing the point here.
This is a bug because as Jeff2365 says, sequence does not wait for any latent functions. As he said, what if the delay is 5 seconds? Will Sequence wait for 5 seconds? What if there are other delays? So unfortunately the gentlemen stating that the Sequence is not triggering because of the delay, is wrong. (And yes, a friend of mine also said the same, and I tested it. This is not related to sequence. It is a macro problem.)
Also this example I use here is not something I need. I got very complex macros that are completely broken and this is NOT related to Sequence or Delay.
If you have two macroes in ANYWHERE of your code, the first macro that triggers BLOCKS the usage of the other macro instances, regardless of a sequence connection. Shortly, you can right now have only ONE of same macro in ONE blueprint.
Also, the fact that the Non-Macro version works and the Macro version doesn’t, is the bug itself too. Let alone the way the pin drag aswell.
You guys can try this aswell. Jeff2365 already knows it but you can just use the Sequence nod. Give first pin a delay of 1 second, and second pin to 0.5 seconds. You will see that 0.5 second delayed second delay comes out first despite being the second sequence pin.