| Previous | Next |
| SCHED_S_TASK_NO_VALID_TRIGGERS | SCHED_S_SOME_TRIGGERS_FAILED |
SCHED_S_EVENT_TRIGGER
SCHED_S_EVENT_TRIGGER indicates that a task uses an event trigger, so it has no fixed next-run time to display. Event-triggered tasks start only when the configured event subscription matches a future event; this status is not a failure and does not mean the trigger has already fired.
Why the schedule view can be misleading
Time, daily, weekly, and calendar triggers have a calculable time boundary. An event trigger instead evaluates an event query, so a conventional “Next Run Time” value cannot represent when the next matching event will occur. The useful evidence is the event log, the trigger’s query, and Task Scheduler’s operational history.
What to validate
- The channel, provider, event IDs, XPath filter, and any value queries in the task XML.
- That the source event actually exists on the target edition of Windows and is enabled in the relevant channel.
- Whether the event is produced under a user, session, or service context different from the one assumed by the task.
Microsoft: Task Scheduler status codes · Microsoft: Trigger types · Microsoft: Task Scheduler schema elements
Looking for a different code? Search another status or error code.