Well, time to reply to this massive notification spamming thread.
This is not how PowerManagement works. I leverage the Quartz.Net library. I simply provide a Quartz formatted CRON schedule and it takes care of the rest. Seeing as how I have not scoured through their source code I can only speculate what is going on.
With the sudden time change, quartz realizes that an event was missed, or what’s known as a misfire. This allows some redundancy, e.g. if a job is set to shutdown at 22:00, and the event fires at 22:01 it will still be processed.
I believe the current behavior is configured to execute a misfire regardless of how much the time is really off. I will work on this and push out a 0.11.5 when I have a chance.