| Previous | Next |
| SCHED_E_TOO_MANY_NODES | SCHED_E_ALREADY_RUNNING |
SCHED_E_PAST_END_BOUNDARY
SCHED_E_PAST_END_BOUNDARY means the task cannot start because the relevant trigger has passed its configured end boundary. The trigger is deactivated after that date and time; it is not merely late for its next scheduled occurrence.
What to check
- The trigger’s start boundary, end boundary, time zone assumptions, and the target machine’s current clock.
- Whether an installer supplied an end date intended for a temporary campaign, maintenance window, or test task.
- Whether all triggers have expired, which can also affect task-expiration behavior and cleanup settings.
Correct response
Update or replace the trigger with a boundary that matches the desired schedule, then confirm that the task remains enabled and has a valid future activation window. Do not simply move the system clock or remove all boundaries without understanding why the end condition was set.
Microsoft: Task Scheduler status codes · Microsoft: EndBoundary · Microsoft: Trigger object
Looking for a different code? Search another status or error code.