Page 1 of 1

Log unmet conditions

PostPosted: Tue Aug 08, 2017 9:31 am
by berkinet
When a Schedule or Trigger Action does not execute because a condition was not met, there is no record in the log. Especially in the case of triggers, it can be difficult to figure out if the event did not take place or if the condition test failed. Adding an option to the Condition page like:
    [x] Log when condition is not met.

It would be really nice to actually be able to log the condition element that failed. But, just noting the fact that it failed to match would be sufficient, and hopefully not too much work.

Thanks

Re: Log unmet conditions

PostPosted: Tue Aug 08, 2017 11:34 am
by jay (support)
We'll add it to the list.