Immediately, if ... option of scheduler

[AGH1965 12]

Recently I complained about the "As soon as possible" option of the scheduler. It was updated in v12.1.31.0, but it is still not doing what it is supposed to. See link.

So a week ago I configured a new daily scan, but this time using the "Immediately, if the time since the last run exceeds a specified value" option activated in combination with a 1 hour setting.  Here a short diary with the disappointing results:

• Saturday: Scheduled scan missed at 20:00.
• Sunday: Previousle missed scan not executed. Why not? Scheduled scan missed at 20:00.
• Monday: Previousle missed scan not executed. Why not? Scheduled scan missed at 20:00.
• Tuesday: Previousle missed scan not executed. Why not? Scheduled scan executed at 20:00.
• Wednesday: Scan executed at 19:05, shortly after booting. Why? Tuesday's scan wasn't missed at all. Scheduled scan missed at 20:00.
• Thursday: Previously missed scan executed at 18:54, shortly after booting. Scheduled scan missed at 20:00.
• Friday: Previously missed scan executed at 18:31, shortly after booting. Scheduled scan missed at 20:00. Computer back online from 21:00 to midnight, but today's missed scan is not executed. Why not? The last scan is more than 1 hour ago.
• Saturday: Previously missed scan executed at 17:31 although the computer has been online the whole afternoon. Why not earlier? The last scan is more than 1 hour ago. Why does the scheduler wait till the last scan is exactly 23  hours ago?

It is absolutely clear that there is a lot wrong with "Immediately, if ..." option of the scheduler.

[Marcos 5,074]

You've already reported it here: https://forum.eset.com/topic/17991-as-soon-as-possible-option-of-scheduler/. Please keep the discussion within the same topic. To prevent duplicate topics on the subject, we'll draw this one to a close.