| Previous | Next |
| DB_E_BOGUS | SCHED_E_TASK_NOT_READY |
SCHED_E_TRIGGER_NOT_FOUND
SCHED_E_TRIGGER_NOT_FOUND means that the requested trigger is not present in the task definition currently held by Task Scheduler. It is normally a lookup or concurrency problem, not a signal that the entire task must be recreated.
Typical causes
- Code cached a trigger identifier or COM object while another administrator, installer, or management tool updated the task.
- The requested trigger was deleted, replaced, or never committed because registration used a different task definition than expected.
- A script addressed a trigger by an assumed position instead of reading the current trigger collection and its identifiers.
Safe handling
Reload the registered task, enumerate its actual triggers, and apply an update only after locating the intended identifier and type. Log the task path and final XML so that a missing trigger can be distinguished from an update made by another component.
Microsoft: Task Scheduler status codes · Microsoft: task definition components · Microsoft: Trigger object
Looking for a different code? Search another status or error code.