New task scheduler interface runs aground

I finished version 3 of the RxReminder task scheduler interface yesterday, and last night it got its first sea trial, and it hit a sandbar.

I entered med Alerts for 8 AM and 8 PM. Here's what the revised scheduler should have done. At 12 midnight, the computer should awaken and run RxReminder. RxReminder would have looked for the first Alert time (8 AM) and put it into the scheduler. Actually, there is a factor called WakeAnticipate: a lead time subtracted from the wakeup time to allow the system time to wake up; the default is one minute. RxReminder should therefore schedule itself to run at 7:59 AM. I checked the computer shortly after 10 AM. I was hoping to see a red X on the reminder's status, indicating the Alert was issued but there was no response. Instead, I saw a question mark, meaning the Alert was not issued. This was disappointing and puzzling.

I looked at the program's log file, and this excerpt was very interesting:

Stopped : 11:26 PM, Monday, June 22, 2009
Started : 12:00 AM, Tuesday, June 23, 2009
Resuming: 12:00 AM, Tuesday, June 23, 2009
Stopped : 12:00 AM, Tuesday, June 23, 2009
Started : 12:00 AM, Tuesday, June 23, 2009
Stopped : 12:00 AM, Tuesday, June 23, 2009
Started : 8:00 AM, Tuesday, June 23, 2009
Resuming: 10:10 AM, Tuesday, June 23, 2009

I stopped the program at 11:26 PM; I wanted a full test of the scheduler, meaning that the program should start itself. At 12 AM it did. Here, something strange happened. The program shut down (not logged), resumed, stopped, started, and stopped again, all at 12 AM. It apparently did schedule the 8 AM Alert, but it should have awakened at 7:59 AM. Instead, it awakened at 8 AM. The Alert is issued at the moment when 7:59 AM changes to 8 AM