| Previous | Next |
| UTC_E_TIME_TRIGGER_ON_START_INVALID | UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE |
UTC_E_TIME_TRIGGER_ONLY_VALID_ON_SINGLE_TRANSITION
Locate the rejected contract: time-trigger ownership
UTC_E_TIME_TRIGGER_ONLY_VALID_ON_SINGLE_TRANSITION (0x87C51031) is a Universal Telemetry Client result from the scenario state-machine trigger validation layer. The symbolic name points to a narrow UTC contract that can be tested directly. The relevant state is time-trigger ownership: one time trigger instance is referenced by more than one transition, making its timer/state ownership ambiguous. This identifies a specific UTC/DiagTrack condition, not a general service failure.
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 | time-trigger ownership |
| Evidence to collect | trigger ID, all referencing transitions, source states, durations and graph serialization |
| Narrow comparison | clone the trigger so each transition owns a distinct timer and compare behavior |
| Do not confuse with | UTC_E_MULTIPLE_TIME_TRIGGER_ON_SINGLE_STATE concerns multiple timers attached within one state |
Comparison with a passing case
- Capture trigger ID, all referencing transitions, source states, durations and graph serialization. Do this before restarting the service or deleting any working directory.
- Perform this one-variable comparison: clone the trigger so each transition owns a distinct timer and compare behavior.
Nearby result: UTC_E_MULTIPLE_TIME_TRIGGER_ON_SINGLE_STATE — concerns multiple timers attached within one state.
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
Author one timer per transition and preserve independent cancellation when a state exits.
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.