| Previous | Next |
| UTC_E_TRACE_NOT_RUNNING | UTC_E_ESCALATION_ALREADY_RUNNING |
UTC_E_REESCALATED_TOO_QUICKLY
Locate the rejected contract: per-scenario escalation cooldown
When UTC_E_REESCALATED_TOO_QUICKLY (0x87C5100E) is returned, the producing layer is DiagTrack scenario-definition processing. The symbolic name points to a narrow UTC contract that can be tested directly. The rejected object or state is per-scenario escalation cooldown, and the specific condition is that the trigger matched again before the configured minimum interval since the previous escalation elapsed. Keep this first HRESULT even if a later service call reports another error.
DiagTrack scenarios are configuration-driven state machines. A scenario definition, its diagnostic rules, referenced profiles, triggers and action graph must all come from a compatible configuration generation. Mixing authoring files or package versions can make an otherwise valid identifier unusable.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | per-scenario escalation cooldown |
| Producing layer | DiagTrack scenario-definition processing |
| Do not confuse with | UTC_E_THROTTLED is event-rate throttling and need not be tied to a completed escalation |
| Evidence to collect | scenario ID, escalation type, prior completion time, cooldown value, trigger timestamps and clock source |
| Narrow comparison | replay the trigger after the cooldown expires without altering any other rule |
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: scenario ID, escalation type, prior completion time, cooldown value, trigger timestamps and clock source.
- Use a passing control on the same Windows build, then replay the trigger after the cooldown expires without altering any other rule.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_THROTTLED — is event-rate throttling and need not be tied to a completed escalation.
Configuration-generation check
Hash the scenario, rules and referenced profile files used and record the UTC process start time. If files changed after the process loaded them, restart only after preserving the prior generation so the comparison remains auditable.
Resolution and regression test
Deduplicate the producer or tune the documented cooldown only when repeated captures are genuinely required.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for DiagTrack scenario-definition processing while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: Windows Event Log query schema
Looking for a different code? Search another status or error code.