| Previous | Next |
| UTC_E_UNABLE_TO_RESOLVE_SESSION | UTC_E_UNAPPROVED_SCRIPT |
UTC_E_THROTTLED
Locate the rejected contract: event-fire rate limiter
UTC_E_THROTTLED has the unsigned value 0x87C51038. In UTC it comes from DiagTrack scenario-definition processing, where event-fire rate limiter owns the decision. The symbolic name points to a narrow UTC contract that can be tested directly. The immediate contract failed because UTC suppressed an event because it arrived more frequently than the configured rate policy permits, so diagnosis should remain at that boundary until a controlled comparison crosses it.
Condition to preserve: The documented condition is “UTC has throttled the event for firing too often.” A comparison run should change that state, not an unrelated component setting.
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 | event-fire rate limiter |
| Producing layer | DiagTrack scenario-definition processing |
| Do not confuse with | UTC_E_SCENARIO_THROTTLED prevents a whole scenario from loading because one trigger is throttled |
| Evidence to collect | event/trigger ID, timestamps, throttle window, count, producer instance and reset boundary |
| Narrow comparison | replay below and above the rate threshold with the same payload |
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: event/trigger ID, timestamps, throttle window, count, producer instance and reset boundary.
- Use a passing control on the same Windows build, then replay below and above the rate threshold with the same payload.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_SCENARIO_THROTTLED — prevents a whole scenario from loading because one trigger is throttled.
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 or pace the producer and treat throttling as expected load control when policy is correct.
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 — reference for DiagTrack scenario-definition processing while interpreting this result.
- Microsoft: UniversalTelemetryClient operational-log guidance — reference for DiagTrack scenario-definition processing while interpreting it.
- Microsoft: Windows Event Log query schema
Looking for a different code? Search another status or error code.