| Previous | Next |
| UTC_E_SCRIPT_MISSING | UTC_E_API_NOT_SUPPORTED |
UTC_E_SCENARIO_THROTTLED
Identify the owning component: scenario-load throttle gate
The code UTC_E_SCENARIO_THROTTLED (0x87C5103B) belongs to DiagTrack scenario-definition processing, inside the Universal Telemetry Client/DiagTrack workflow. Correlate this HRESULT with the exact request attempt that returned it. It identifies scenario-load throttle gate and reports that a trigger associated with the scenario is currently throttled, so UTC blocks loading the scenario; it does not by itself prove that all Windows diagnostic data collection is unavailable.
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.
What to capture before retrying
| UTC diagnostic field | Value |
|---|---|
| Producing layer | DiagTrack scenario-definition processing |
| Owning state or object | scenario-load throttle gate |
| Evidence to collect | scenario and trigger IDs, throttle state/window, producer rate, prior firings and configuration version |
| Narrow comparison | wait for reset or use a fresh controlled trigger instance and attempt the load once |
| Do not confuse with | UTC_E_THROTTLED reports suppression of an individual event after the scenario is loaded |
Prove the condition
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: scenario and trigger IDs, throttle state/window, producer rate, prior firings and configuration version.
- Use a passing control on the same Windows build, then wait for reset or use a fresh controlled trigger instance and attempt the load once.
- 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 — reports suppression of an individual event after the scenario is loaded.
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.
Confirm the repair
Correct trigger frequency or throttle configuration before repeatedly reloading the scenario.
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 it.
- Microsoft: UniversalTelemetryClient operational-log guidance
- Microsoft: Windows Event Log query schema
Looking for a different code? Search another status or error code.