My guess is that it is being triggered both by the 300-second delay AND each day – meaning, you’ve got the rule running multiple times and not just the every 300-second delay that you wanted. So, for each day that this rule has been created, it is firing at 10:53AM regardless of the $FiveMinuteTimer changed to false. This would create it running multiple times and not in keeping with only the 300-second delay.
If you delete the rule and only establish the trigger based on it turning false (you could set it to true on a dashboard for example – but only once!) and it would only trigger every 300 seconds.
Hmmm. That makes sense! I’ll re-do the rule and just trigger it from the variable once. Is there really a need on my part to worry that something might cause it to break or not fire at some random 300 second mark? That’s the only reason I added the once every day, thinking if it stopped working at least it would restart the next day.
I have a similar rule that does stop every once in a while for no apparent reason and I currently manually trigger it again by updating the variable it uses. I’m thinking about creating a separate rule to ensure it stays active.