What does HRESULT 0x87C51022 (UTC_E_TRIGGER_MISMATCH) mean?

UTC_E_TRIGGER_MISMATCH

Map the code to the scenario graph: trigger type binding

When UTC_E_TRIGGER_MISMATCH (0x87C51022) is returned, the producing layer is scenario state-machine trigger validation. A reliable investigation preserves the producing action before any cleanup runs. The rejected object or state is trigger type binding, and the specific condition is that a supplied trigger instance is not of the type required by the transition or forwarder. Keep this first HRESULT even if a later service call reports another error.

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.

Data needed for triage

Reproduce without collateral changes

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture expected/actual trigger type, producer, transition ID, serialized payload and configuration generation. Do this before restarting the service or deleting any working directory.
3. Perform this one-variable comparison: construct the trigger through the expected producer while leaving payload values unchanged.
4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created.

Nearby result: UTC_E_FORWARDER_PRODUCER_MISMATCH — concerns the forwarding object rather than the trigger payload.

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.

Fix the contract

Bind each transition to the correct trigger factory and discard cached triggers after reload.

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 this result.
• Microsoft: Querying Windows Event Log — reference for scenario state-machine trigger validation while interpreting it.
• Microsoft: Windows Performance Recorder