Share via

Task Scheduler run unexpectedly after server reboot following DST change

Anonymous
2023-11-14T06:20:59+00:00

The below issues happened on Windows server 2016 and 2019

  • There are jobs scheduled to run from Mon to Fri (with setting 'Run task as soon as possible after a scheduled task is missed' enabled) but got triggered on 20231105(Sun) after the server reboot following the DST change.
  • There are jobs with the setting 'Run task as soon as possible after a scheduled task is missed' disabled but the job task code becomes 2147020576 or the last run time of the job got changed after the server reboot following the DST change.
  • Could you please advise if this is a known issue to Microsoft? If yes, may I know if there is a fix to the issue?
Windows for business | Windows Server | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-11-15T02:39:38+00:00

    Hello,

    1.The behavior you're describing is common and can be attributed to the way the Task Scheduler handles missed tasks during DST changes.

    The "Run task as soon as possible after a scheduled task is missed" setting allows the Task Scheduler to catch up on missed tasks when the system becomes available. If the server was unavailable during the normal schedule, the missed task could be triggered when the server is back online. If the time adjustment is not handled correctly, it might lead to tasks running on the wrong day.

    1. The DST change can cause time adjustments, and if the task scheduler is not handling these changes correctly, it might lead to errors or unexpected behavior.

    3.If possible, adjust the scheduling of critical tasks to avoid the time when DST changes occur.

    Day interval schedules may be impacted by DST changes, especially if they occur at the beginning or end of a day. Instead, use specific time schedules or, better yet, UTC-based schedules to avoid discrepancies.

    Check the box labeled "Synchronize across time zones", then the task is scheduled by UTC.

    Image

    Note: The Day interval schedules the next run 24 hours from the previous scheduled time, depending on the settings. This can lead to the times being changed during DST. The Specific day(s) of the week will run at the same time on each of the specified days.

    Regards,

    Karlie

    0 comments
  2. Anonymous
    2023-11-15T09:02:09+00:00

    Hi Karlie,

    Thanks for the information:) Could you please elaborate more on "If the time adjustment is not handled correctly" and "If the task scheduler is not handling these changes correctly"? Does that mean this is not something that we can control from the setting but the task scheduler can't handle the DST change correctly?

    Thank you.

    0 comments
  3. Anonymous
    2023-11-17T06:19:09+00:00

    Hello!

    The issue with scheduled tasks after DST changes is a known Task Scheduler issue where the calculation of the next run time for the task does not handle DST correctly.

    It is being investigated and reported to Microsoft.

    Regards,

    Karlie

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2023-11-17T07:55:27+00:00

    Thank you for the confirmation!

    0 comments