| Previous | Next |
| UTC_E_TIME_TRIGGER_ONLY_VALID_ON_SINGLE_TRANSITION | UTC_E_MULTIPLE_TIME_TRIGGER_ON_SINGLE_STATE |
UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE
Where the UTC workflow stopped: time-trigger duration validator
When UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE (0x87C51032) is returned, the producing layer is scenario state-machine trigger validation. The key question is which UTC object rejected the request. The rejected object or state is time-trigger duration validator, and the specific condition is that the configured duration falls outside the accepted inclusive range of one second through fifteen minutes. 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.
Evidence to preserve
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | time-trigger duration validator |
| Producing layer | scenario state-machine trigger validation |
| Do not confuse with | UTC_E_TRACE_MIN_DURATION_REQUIREMENT_NOT_MET is a runtime trace-age check, not invalid timer configuration |
| Evidence to collect | raw duration value/unit, serialized XML, schema version, transition ID and authoring-tool output |
| Narrow comparison | test boundary values at one second and fifteen minutes before the rejected value |
Controlled reproduction
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: raw duration value/unit, serialized XML, schema version, transition ID and authoring-tool output.
- Use a passing control on the same Windows build, then test boundary values at one second and fifteen minutes before the rejected value.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_TRACE_MIN_DURATION_REQUIREMENT_NOT_MET — is a runtime trace-age check, not invalid timer configuration.
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.
Correction and verification
Store the duration in the documented unit and keep it within the accepted range.
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
Looking for a different code? Search another status or error code.