Getting back to the real subject of discussion the recording of Countdown finished today at 14:59 and was immediately Flattened, similarly for 32 Brinkburn Street at 15:00
The 15:05 scheduled scan started but failed for some reason just after the start of the decrypt scan line 210
The 15:25 scheduled scan ran normally decrypting two recordings
I don't like the decrease in frequency of scheduled to 20 minutes but do like the offsetting from the hour to reduce the likelihood of end of recording scans colliding with scheduled scans, I still depend on the scheduled runs to actually do the actual decryption and scheduling of ad detection so still prefer a more frequent scan to reduce chance of long waits. I would prefer 5-59/10 or 5-59/15.
On a related theme would it be possible to initiate a run of Auto (and Detectads) at system boot to handle any processing that had not been completed because of the system shutting itself down after a scheduled recording.
I can't immediately see why that 15:05 scheduled scan failed.. is that with the debugging level set to max?
I have always wanted to reduce the frequency once the triggering mechanism is working properly but I can see that it wouldn't help your situation since flatten is (currently) implemented as a post-decryption-scan plugin.
A scan following boot is definitely a good idea. Since detectads is a plugin it would run too.