When selecting a periodic trigger with all 60 minutes selected, RM generates the following error:
Why not just use the every "n" minutes trigger and trigger the rule every minute?
That's what I ended up doing. Started with "each minute" so I could have the events happen at :00 seconds. "Every n minutes" doesn't guarantee which second the event will happen on, just that it happens once a minute. In my case, the events I was trying to sync at :00 are now firing at :13 and :15 seconds into each minute. Slightly different outcome, and not ideal when trying to sync two events to happen at the same time.
Just a thought, but couldn't you make the first rule trigger the second rule?
I'm only suggesting this because if you do configure the rules as you wish, they cannot run simultaneously as only one event can occur at a time. Just a thought. 
Doesn't fix the bug though.........
1 Like
Ha! Itās a database column size limit set at 120. Iāll have figure out what size it would need to be. Some bug ā- bah humbug.
1 Like
Merry Christmas to you too. 
We either need a 200 size column or someway to make every n minutes be st :00
1 Like
The cron string for every n minutes schedules for :11. That could be changed to :00. Not sure why you are seeing :13.
Could have been wrong, I was testing a handful of things and may have been remembering the wrong time stamps. If they are synced up and both happen at :11 then that will work fine.
Donāt get too invested in :11, going to change it to :00.
2 Likes
