[dnanian]

I understand, and I do the best I can to help. I've done what we documented myself, on many different machines, without this kind of problem. I've attempted to duplicate your issue, and I've been unable to. (Two of the systems I tested had BT mice/keyboards, two had wired, one had non-Apple [MS].)

If I can't reproduce the issue, and it's not happening to a lot of people, it's really difficult for me to provide support above and beyond what I've done. It's not that I don't want to help: it's just that we're simply scheduling a program to run with a system facility: cron. If cron then fails to run us -- or the system doesn't allow us to run after wake in your configuration -- there's nothing we can "tweak" to convince it to do so other than the time between wake and run.

Apart from clean installing to another drive/partition and trying it in a pristine configuration -- something I'm sure you'd not want to do -- the only thing I can suggest is creating a new, fresh account, logging out of your regular one and into that, and scheduling as that user (you'll have to re-enter your registration info). Perhaps something you're running is interfering.