Bug: Rule Machine, Delay per Mode using a variable

Found a bug, hope it helps...

In RM5, I created Delay Per Mode action. I then chose to set per variable instead of inputting values. Any variable of type number or datetime, either locally or hub level, causes a Java exception to be thrown per the logs and kills the execution of the rule.

Interestingly, it does not cause a Java exception on a normal Delay using a variable (no modes).

Take care,
Marty

I'll look into it.

This will be fixed in the next release.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.