Debug Log #10: A Post Didn't Publish On Schedule, and I Can't Fully Explain Why
One post out of thirty didn't go out on schedule, and the exit code it left behind means "something killed this process," not "something went wrong inside it." I found this by accident, checking in on the blog two days after it should have published. Here's what I can establish and what I genuinely can't. Metric Value Scheduled time Oct 17, 9:00 PM Actual run time Oct 19, 9:24 AM (almost 36 hours late) Exit code 3221225786 (a control-C-style forced termination) Post created on Blogger? No -- confirmed via API, no draft, live, or scheduled version existed Other 29 scheduled runs since August All exit code 0 What I can confirm The task didn't fire at 9 PM on the 17th, which almost certainly means the machine was asleep or off at that moment -- the same root cause this blog's very first scheduled-task post documented back in August. The "wake and catch up" setting did its job eventually, just thirty-six hours later than intended, when...