| 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. The symbolic name points to a narrow UTC contract that can be tested directly. 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.
Time, event and forwarded triggers participate in a scenario state machine. Their type, ownership, source state and transition cardinality are configuration contracts; changing the observed event cannot repair an invalid graph.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario state-machine trigger validation |
| Owning state or object | trigger-definition lookup |
| Evidence to collect | 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 |
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.
- Use a passing control on the same Windows build, then replace the reference with one known trigger from the same package.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_SCENARIODEF_NOT_FOUND — means the enclosing scenario is absent.
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 state at failure.
Resolution and regression test
Deploy the missing trigger definition or correct the reference; an empty placeholder is not a valid repair.
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.