From: Dana Okafor, Finance, Fernhill Garden Supply
"The cash report is supposed to land in my inbox at 7:00 every weekday. In the first two weeks of March it didn't come on several mornings, and nobody changed anything. scheduler.log has one JSON line per event the job wrote. Which mornings did we miss, and why?"
The explanations people have suggested:
- A. The job ran at the wrong hour.
- B. A run crashed and left its lock, and later runs skipped until someone removed it.
- C. The mail service's rate limit stopped the report.
- D. The scheduler doesn't run on some weekdays.
Your answer: the letter the log supports, with the number of missed mornings as evidence.
This case study is the other side of scheduling. A job that runs unattended has failed, and its log is the only witness. The log is in JSON Lines form: one JSON object per line, each with a UTC timestamp ts and an event, and some with a reason or an error.
Decide what counts before you count. A morning is missed when no sent event happened that day; a retry that ended in a sent cost nothing. Logs also have damage: a line cut off mid-write, a blank line, and a day where the report went to two people.
period in the setup holds the first and last day Dana is asking about.
Out: 'locked'. Each line parses on its own, so one damaged line doesn't spoil the rest.