Share via

Task scheduler executes reputations for disabled/expired triggers after manual run

Sireesh Cheruku 20 Reputation points
2026-01-20T12:00:34.22+00:00

Issue: Windows Task Scheduler ignores the "Disabled" state of a Trigger if the task is run manually, causing it to enter an indefinite repetition loop even after the Trigger has expired.

Environment:

  • Windows Server 2022 (Task Scheduler)

User permissions: Admin

Steps to Reproduce:

Create a Task with a Daily Trigger (Start: Jan 1st).

In Trigger Advanced Settings, set "Repeat task every: 6 hours" for a "Duration: 1 Day".

Set an Expire Date for the Trigger (e.g., Jan 9th).

Disable the Trigger (or let it expire naturally).

Manually Run the task (Right-click Task > Run) at any time after the expiration/disable date (e.g., Jan 10th).

Observed Behavior: The manual run successfully executes the task once (expected). However, it also reactivates the repetition logic. The task begins repeating every 6 hours indefinitely from the time of the manual run, despite the controlling Trigger being Disabled/Expired.

Expected Behavior: A manual run should execute the Action once. It should not engage the Repetition interval of a Trigger that is currently Disabled or Expired.

Windows for business | Windows Server | Performance | Other
0 comments

Answer accepted by question author

Quinnie Quoc 11,060 Reputation points Independent Advisor
2026-01-20T12:36:27.9333333+00:00

Dear Sireesh Cheruku,

Thank you for your detailed description of the issue with Task Scheduler on Windows Server 2022. Based on your steps, the observed behavior occurs when a task is manually run after its trigger has expired or been disabled. While the expectation is that the task should execute only once, the repetition logic defined in the trigger is still applied, resulting in an indefinite loop.

This behavior is by design in certain versions of Task Scheduler, where manual execution bypasses the trigger state but still references its repetition settings. To avoid this, I recommend creating a separate “On‑Demand” task without repetition configured, or disabling the repetition option entirely when tasks may need to be run manually. Alternatively, you can export the task XML, remove the repetition element, and re‑import it for manual execution scenarios.

I also suggest keeping your server updated with the latest cumulative patches, as improvements to Task Scheduler behavior are periodically included. If the issue persists, please share the exported XML configuration so our support team can analyze further.

Please click "Accept the answer" to support me. Thank you very much.

Kind regards,

QQ.

Was this answer helpful?

1 person found this answer helpful.

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Quinnie Quoc 11,060 Reputation points Independent Advisor
    2026-01-21T09:55:26.3133333+00:00

    Dear Sireesh Cheruku,

    Thank you for your follow‑up question. Based on the current design of Task Scheduler in Windows Server 2022, manual execution of a task does not fully respect the disabled or expired state of its trigger. This means that the repetition logic can still be invoked even after the trigger has expired, which aligns with the behavior you observed.

    At this time, there is no definitive fix available to change this behavior, and the supported approach is to implement workarounds such as creating a separate “On‑Demand” task without repetition or modifying the XML to remove the repetition element. I understand this may not be ideal, but these methods are the recommended way to ensure manual runs execute only once.

    I also suggest monitoring future cumulative updates and release notes, as improvements to Task Scheduler are periodically introduced. If strict control is required in your environment, using alternative scheduling mechanisms or scripts may provide more predictable results.

    I appreciate your patience and collaboration. Please click "Accept the answer" to support me. Thank you very much.

    Kind regards,

    QQ.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.