| Previous | Next |
| UTC_E_TRIGGER_MISMATCH | UTC_E_SIF_NOT_SUPPORTED |
UTC_E_TRIGGER_NOT_FOUND
Locate the rejected contract: trigger-definition lookup
The code UTC_E_TRIGGER_NOT_FOUND (0x87C51023) belongs to scenario state-machine trigger validation, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. The symbolic name points to a narrow UTC contract that can be tested directly for this HRESULT. It identifies trigger-definition lookup and reports that the scenario references a trigger identifier that is absent from the loaded configuration; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.
Time, event and forwarded triggers participate in a scenario state machine for this HRESULT. Their type, ownership, source state and transition cardinality are configuration contracts; changing the observed event cannot repair an invalid graph for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario state-machine trigger validation |
| Owning state or object | trigger-definition lookup |
| Decisive evidence | trigger ID/name, referencing state/transition, scenario package, forwarder registry and load diagnostics |
| Narrow comparison | replace the reference with one known trigger from the same package |
| Do not confuse with | UTC_E_SCENARIODEF_NOT_FOUND means the enclosing scenario is absent |
The AllStat message names the immediate condition as “Requested trigger cannot be found” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.
Comparison with a passing case
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: trigger ID/name, referencing state/transition, scenario package, forwarder registry and load diagnostics for this HRESULT.
- Use a passing control on the same Windows build, then replace the reference with one known trigger from the same package for this HRESULT.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state for this HRESULT.
The most informative neighbor is UTC_E_SCENARIODEF_NOT_FOUND. The distinction is concrete: UTC_E_SCENARIODEF_NOT_FOUND means the enclosing scenario is absent for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.
Platform-state note
Capture capability and identity state at the moment this result is returned. Session, container, service and destination state can change asynchronously, so a later successful query does not describe the failed generation for this HRESULT.
Resolution and regression test
Deploy the missing trigger definition or correct the reference; an empty placeholder is not a valid repair for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.
Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result for this HRESULT.
- the same request now produces its documented success or nonfatal status without a second hidden retry
- the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
- teardown followed by a second run does not reuse stale state or recreate trigger-definition lookup
- the nearby condition remains distinguishable: UTC_E_SCENARIODEF_NOT_FOUND means the enclosing scenario is absent
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for scenario state-machine trigger validation while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario state-machine trigger validation while interpreting it.
- Microsoft: Querying Windows Event Log
- Microsoft: Windows Performance Recorder
Looking for a different code? Search another status or error code.