What does HRESULT 0x87C51025 (UTC_E_DELAY_TERMINATED) mean?

UTC_E_DELAY_TERMINATED

Interpret the result in context: DelayAction timer

UTC_E_DELAY_TERMINATED (0x87C51025) is a Universal Telemetry Client result from the scenario action execution layer for this HRESULT. Start by locating the exact scenario-engine boundary that emitted this Value. Here the relevant owner is DelayAction timer: a scheduled delay was cancelled before its expiration because the scenario, service or escalation was ending for this HRESULT. This is narrower than a generic failure of Connected User Experiences and Telemetry for this HRESULT.

Scenario actions run under service-controlled identity, timeout and cancellation rules for this HRESULT. The useful evidence is the exact action instance and its child process or script state, not a later generic service event for this HRESULT. stdout, stderr and native exit values should be retained separately from the UTC HRESULT 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.

Build a minimal evidence set

The AllStat message names the immediate condition as “The delay action was terminated” 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.

Run an A/B check

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture delay duration, timer start, cancellation source, state transition, shutdown event and elapsed time for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
3. Perform this one-variable comparison: allow a short delay to expire normally, then cancel the scenario during a longer delay for this HRESULT.
4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.

The most informative neighbor is UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE. The distinction is concrete: UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE rejects a configured trigger duration before runtime 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.

Child-action accounting

Keep process creation, job assignment, timeout, cancellation, exit code and output capture as separate timestamps for this HRESULT. That sequence reveals whether the child failed itself, was terminated by UTC or never started for this HRESULT.

Safe remediation

Treat cancellation as lifecycle control and ensure following actions do not run from a stale callback 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.

Restarting Windows, clearing every ETL file or disabling diagnostic policy is not a justified first response to this result. Those actions destroy evidence and can change several independent UTC gates at once 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 DelayAction timer
• the nearby condition remains distinguishable: UTC_E_TIME_TRIGGER_INVALID_TIME_RANGE rejects a configured trigger duration before runtime

Technical references

• Microsoft Open Specifications: Windows error-code registry — reference for scenario action execution while interpreting this result.
• Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario action execution while interpreting this result.
• Microsoft: UniversalTelemetryClient operational-log guidance — reference for scenario action execution while interpreting it.
• Microsoft: About Windows Error Reporting

Looking for a different code? Search another status or error code.