How do I check whether a Windows scheduled task ran?
Use the exact task path and name to inspect both its definition and runtime information. A task being Ready means it is available to run; it does not prove that its last execution produced the intended business result.
Instructions
1. Locate the exact task
Replace the example path and name with the existing authorised task.
Get-ScheduledTask -TaskPath '\ExampleApp\' -TaskName 'HealthCheck' | Select-Object TaskPath, TaskName, State, Actions, TriggersInspect the configured action and schedule. Task actions may contain sensitive arguments, so do not publish them unredacted.
2. Read execution information
Use the same path and name to avoid confusing tasks with identical names in different folders.
Get-ScheduledTaskInfo -TaskPath '\ExampleApp\' -TaskName 'HealthCheck' | Select-Object LastRunTime, LastTaskResult, NextRunTime, NumberOfMissedRunsReview when it last ran and the reported result code. Interpret nonzero values using the task and Windows documentation.
3. Verify the intended output
Check the application log, generated record or documented health result. A zero exit code can confirm that the launched command reported success while still failing to prove that every intended downstream action occurred.
Check the result
- The exact task definition and last runtime match the expected schedule.
- The task’s real output or application result is present and correct.
Troubleshooting
- The task was never triggered
- Review enabled state, conditions, schedule and whether the server was available at the scheduled time.
- The task works interactively but not on schedule
- Compare the run-as identity, working directory, environment and access rights; do not embed a password in task arguments.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.