@bravenel I found a work-around for the problem. Sharing this in case it helps others that are having the problem and in case it provides you useful information for identifying the root-cause.
The original rule had 3 triggers: 2 triggers were based on sunrise; 1 trigger was a cron expression.
I broke the rule into 2 rules:
- The first rule has the 2 triggers that are based on sunrise. This rule also contains all the logic I want executed.
- The second rule has the cron trigger and runs the first rule whenever it is triggered.
I've been running this way for about a week, and I am no longer seeing the "pile up" of scheduled jobs, so it looks like the problem has something to do with having a rule with both sunrise-based triggers and a cron-based trigger.
Hope this helps!
Marc
Here are screenshots of the 2 rules referenced above.
First rule;
Second rule:
