| Previous | Next |
| SCHED_E_PAST_END_BOUNDARY | SCHED_E_USER_NOT_LOGGED_ON |
SCHED_E_ALREADY_RUNNING
SCHED_E_ALREADY_RUNNING means an instance of the task is already active and the requested start could not create another one under the current task policy. It does not say whether the existing process is healthy, hung, waiting for input, or intentionally long-running.
Understand the instance policy
Task Scheduler can run instances in parallel, queue a new instance, ignore a new request, or stop an existing instance before starting another. The selected MultipleInstancesPolicy determines whether an overlap is allowed, so the correct remedy depends on the task’s concurrency contract.
Diagnose before changing the policy
- Identify the active instance, start time, action command line, and last scheduler event.
- Check whether an execution-time limit, child process, or external resource wait prevents normal completion.
- Choose a policy that preserves idempotency and data integrity; parallel execution can corrupt work designed for a single writer.
Microsoft: Task Scheduler status codes · Microsoft: MultipleInstances policy · Microsoft: task states
Looking for a different code? Search another status or error code.