| Previous | Next |
| SCHED_S_TASK_READY | SCHED_S_TASK_DISABLED |
SCHED_S_TASK_RUNNING
Scheduled task currently has a running instance
SCHED_S_TASK_RUNNING is HRESULT 267009 (0x00041301) from winerror.h. The documented description is “The task is currently running.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.
In the Task Scheduler state query, this result means that the task is currently running. Treat it as a distinct branch whose postcondition must be proven before subsequent operations begin.
Where the status is encountered
- Task Scheduler status monitoring; log the exact method and object state instead of interpreting the constant outside that contract.
- Deployment or maintenance task validation; log the exact method and object state instead of interpreting the constant outside that contract.
- Automation that reads task state before starting work; log the exact method and object state instead of interpreting the constant outside that contract.
Evidence to preserve
- Preserve running instance GUID.
- Preserve engine process identifier.
- Preserve start time and duration.
- Preserve multiple-instance policy.
- Preserve current action and task history event.
What must be true before accepting it
Verify that the returned instance is genuinely active and the caller does not confuse queued, ready, or stale historical state with execution. The caller should make the acceptance test explicit in code and telemetry.
Inspect the current generation of every affected object before deciding what happens next.
Correct handling and recovery
Inspect running instances, start time, engine PID, and last heartbeat or operational event. Wait, monitor, or stop through Task Scheduler APIs rather than launching a duplicate instance outside the service.
Distinguish protocol continuation from retrying the entire high-level operation.
Difference from nearby results
SCHED_S_TASK_READY is idle and eligible; SCHED_S_TASK_TERMINATED describes the previous run ending by user action.
Practical scenario
An administrator checks a maintenance task before deploying an update. The status is running, so deployment waits for the instance ID to finish instead of starting a second maintenance process.
References
- Microsoft: Task Scheduler error and success constants — official Microsoft material relevant to this HRESULT.
- Microsoft: Task Scheduler reference
- Microsoft: HRESULT values
Looking for a different code? Search another status or error code.