| 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 for this HRESULT. 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 for this HRESULT.
Boundary 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 for this HRESULT. Mixing authoring files or package versions can make an otherwise valid identifier unusable for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
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 |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “UTC has throttled the event for firing too often” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.
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 for this HRESULT.
- Use a passing control on the same Windows build, then replay below and above the rate threshold with the same payload for this HRESULT.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state for this HRESULT.
The most informative neighbor is UTC_E_SCENARIO_THROTTLED. The distinction is concrete: UTC_E_SCENARIO_THROTTLED prevents a whole scenario from loading because one trigger is throttled for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.
Configuration-generation check
Hash the scenario, rules and referenced profile files used for this HRESULT, 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 for this HRESULT.
Resolution and regression test
Deduplicate or pace the producer and treat throttling as expected load control when policy is correct for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.
Deleting the working directory, killing all ETW sessions or retrying in a tight loop can suppress this result temporarily while leaving the underlying lifecycle defect intact for this HRESULT.
- the same request now produces its documented success or nonfatal status without a second hidden retry
- the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
- teardown followed by a second run does not reuse stale state or recreate event-fire rate limiter
- the nearby condition remains distinguishable: UTC_E_SCENARIO_THROTTLED prevents a whole scenario from loading because one trigger is throttled
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.