Timing Edge Cases

[calebsyring]

We need to brainstorm and test edge cases to do with run_due_checks timing. Especially:

• How to handle edge cases involving paused monitors
• How to "catch up" if the system is down for a period of time
• Anything else?

[calebsyring]

Editing the title because it's likely handling timing edge cases will involve run_checks as well.

[calebsyring]

Based on evaluating some logs this weekend, the scheduling is highly accurate, but the second part of the timing is linked to when the schedule was originally created. So when you tell it to run every minute, it doesn't actually run on the minute. It runs on the 13th second because whenever you created the schedule it was on the 13th second.

12:00:13
12:01:13
12:02:13
...

Two things:

• I think perhaps we should change the cron expression to "0 * * * * *"
• There's also a "flexible timing window" setting we should make sure is disabled