Cascading failure bug?


In this Hyperion fight I have spectre, weakness, armour break & degen, shouldn’t I get exhaustion before the degen?

And in this domino fight I have spectre and weakness, shouldn’t it be spectre and armour break?
Maybe I’m misunderstanding how the node works?
0
Comments
I understood that the debuffs come in a certain order.
I've noticed this just occurring again, as I was just in an aq fight and got degen as the first debuff, before spectre or any other..
It seems to be in a random order now?
The description specifies per timer it should appear in the order of
Spectre, armor break, weakness, exhaustion, passive degen.
Please look into this.