BT bug? Multiple decorators fail to abort, but custom decorator succeeds

As you can see in the screenshot, my top priority sequence is failing to abort lower priority tasks despite both decorators going to “pass.”

I did verify that both conditions are going to “fail” and then back to “pass.”

I tried replacing the two conditions with a single custom decorator. It’s just a simple AND operation:

This should do the same thing. But with only this change, now it’s working as intended. It’s not an ideal solution though since it obfuscates what the conditional keys are.

So the question is, why is this happening? Is there something I’m not understanding or is it just an underlying bug in the BT?