Required Expression Not Evaluating Correctly?

[bravenel]

@bertabcd1234

avoid using local variables in required expressions. They don't generate events, so even if their values change, the required expression won't "see" that so may not get updated until something else happens.

The required expression would only be evaluated when the rule is opened in the UI, never otherwise, so this would fail.

Will look into the error thrown...

[zsaffir]

Thanks for the tip - I'll stop using global variables in required expressions.
In case it helps, I did try the same thing with global variables in the regular expression but I get the same error.

[bravenel]

@zsaffir

I'll stop using global variables in required expressions.

Hub Variables are fine, just not local variables.

[zsaffir]

Sorry, meant to write local - just typed the exact opposite of what I intended.

[zsaffir]

Any updates on this?

[bravenel]

On the to-do list.

[bravenel]

This is going to be fixed in an upcoming release,

The resolution will be that it will still throw an error to the logs, like this:

However, unlike now, that will not be a fatal error. Instead, whatever date/time is in the past will simply not be scheduled. This will work for triggers and Required Expression conditions.

[zsaffir]

Sounds great - looking forward to the release! Thank you!

[bravenel]

Perhaps worth pointing out that the evaluation of a Between Two Dates conditions doesn't care about a date in the past. It was only the scheduling of Required Expression elements that caused this problem.