| Previous | Next |
| UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE | UTC_E_BINARY_MISSING |
UTC_E_MULTIPLE_TIME_TRIGGER_ON_SINGLE_STATE
Interpret the result in context: state timer cardinality
The code UTC_E_MULTIPLE_TIME_TRIGGER_ON_SINGLE_STATE (0x87C51033) belongs to scenario state-machine trigger validation, inside the Universal Telemetry Client/DiagTrack workflow. Start by locating the exact scenario-engine boundary that emitted this value. It identifies state timer cardinality and reports that a state contains more than one time-trigger definition where the engine permits only one; 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.
Build a minimal evidence set
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario state-machine trigger validation |
| Owning state or object | state timer cardinality |
| Evidence to collect | state ID, attached triggers, transition targets, durations and configuration merge history |
| Narrow comparison | retain one timer and convert the other condition to a different supported trigger in a test scenario |
| Do not confuse with | UTC_E_TIME_TRIGGER_ONLY_VALID_ON_SINGLE_TRANSITION means one timer was reused across transitions |
Run an A/B check
- Associate this result with one request, one scenario version and one service process ID.
- Save state ID, attached triggers, transition targets, durations and configuration merge history and the first lower-level HRESULT if one exists.
- Change no policy, provider set or destination except for this test: retain one timer and convert the other condition to a different supported trigger in a test scenario.
- Compare the produced artifacts and operational events, not only the top-level return value.
Nearby result: UTC_E_TIME_TRIGGER_ONLY_VALID_ON_SINGLE_TRANSITION — means one timer was reused across transitions.
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.
Safe remediation
Redesign the state graph so one timer owns time-based departure from each state.
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.