False RM Trigger

After latest platform upgrade to the 2.4.1.176 version at least one rule is triggered when it must not.
Here is a (very simple) rule in question:

And here is a related log:

Event is detected.
Rule is not triggered because condition is false (this is correct).
But rule is immediately triggered with the condition still reported false (ROBLEM!)

Clinking on DONE and/or UPDATE RULE buttons is not fixing the issue like it did in a past.

@bravenel do you need any additional info before I will rebuild this rule from scratch?

And now I am not sure what else is broken because at least two latest updates touched exactly Conditional Triggers area. I have too many rules with Conditional Triggers.

UPDATE.
I am sorry for the noise, I missed this was already reported and even reproducible.

This bug found and fixed. Next release...

4 Likes