Bug with Occurrence in Rules (When, Then)

We have a set of rules with When, Then

They all act well as long as you DON’T use occurrence with or without repetition.

It seams that rules which have not manage to occur/happen for whatever reason (gateway off, system off …) they are not reset/erased, purged… and the events occur when ever it is possible after connections, or situation is back to normal.

If a rule is queued to happen then let’s say it would be normal. BUT if you have a rule with time conditions such as Every Monday at 8AM from this day to that day === DO this rule … THEN it is ridiculous to get this rule happen/occur on Tuesday when connection is back or conditions reunited !

1 Like

Any feedback on this topic, please?

@Don and @Pierre , any clue?

Hi Payami, indeed this shouldn’t happen. Can you raise an issue on it at Sign in to GitHub · GitHub ? Can you describe it in a reproducable way? Thanks for pointing out!

There was already an issue (#1242) about rule actions being triggered at startup for which a fix just got merged.