| Previous | Next |
| UTC_E_REESCALATED_TOO_QUICKLY | UTC_E_PERFTRACK_ALREADY_TRACING |
UTC_E_ESCALATION_ALREADY_RUNNING
Where the UTC workflow stopped: single active escalation instance
The code UTC_E_ESCALATION_ALREADY_RUNNING (0x87C5100F) belongs to DiagTrack scenario-definition processing, inside the Universal Telemetry Client/DiagTrack workflow for this HRESULT. The decisive question is which UTC object rejected the request for this HRESULT. It identifies single active escalation instance and reports that a second escalation for the scenario arrived while its prior escalation still owned the working state; it does not by itself prove that all Windows diagnostic data collection is unavailable for this HRESULT.
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.
Evidence to preserve
| UTC diagnostic field | Value |
|---|---|
| Producing layer | DiagTrack scenario-definition processing |
| Owning state or object | single active escalation instance |
| Decisive evidence | scenario and escalation IDs, active action, working directory, process/session IDs and cancellation state |
| Narrow comparison | allow the first run to complete, then submit exactly one new trigger |
| Do not confuse with | UTC_E_ESCALATION_DIRECTORY_ALREADY_EXISTS can remain after a crashed run even when no escalation is active |
The AllStat message names the immediate condition as “A scenario failed to escalate: This scenario is already running an escalation” 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.
Controlled reproduction
- Associate this result with one request, one scenario version and one service process ID for this HRESULT.
- Save scenario and escalation IDs, active action, working directory, process/session IDs and cancellation state and the first lower-level HRESULT if one exists for this HRESULT.
- Change no policy, provider set or destination except for this test: allow the first run to complete, then submit exactly one new trigger for this HRESULT.
- Compare the produced artifacts and operational events, not only the top-level return Value.
The most informative neighbor is UTC_E_ESCALATION_DIRECTORY_ALREADY_EXISTS. The distinction is concrete: UTC_E_ESCALATION_DIRECTORY_ALREADY_EXISTS can remain after a crashed run even when no escalation is active 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.
Correction and verification
Serialize escalation requests and make completion/cleanup observable before accepting another 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.
Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result 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 single active escalation instance
- the nearby condition remains distinguishable: UTC_E_ESCALATION_DIRECTORY_ALREADY_EXISTS can remain after a crashed run even when no escalation is active
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.