The scheduler was down at 2 a.m. Did the invoices run?

transcript

Your scheduler was down at 2 a.m. Did the nightly invoices go out?

1:55. The whole scheduler fleet goes down. 2:00. Nightly invoices is due. Nobody claims it. 2:10. The schedulers come back. And find a missed run.

With no rule, the system has to guess. It might skip it silently. Or fire a burst of stale runs. So each job declares a misfire policy, up front.

Run once. Run it now, one time. That's what nightly invoices declared. Run all. Catch up every missed occurrence. Good for hourly data loads. Skip. Nobody wants yesterday's reminder.

One more 2 a.m. trap. Daylight saving. Schedulers use the database's clock, and each job's own time zone. So a 2 a.m. job doesn't run twice when clocks go back.

Run once, run all, or skip. Each job picks one when it's created. Recovery isn't a guess. Every job says what a missed run means.

Full breakdown in the lecture.