| Previous | Next |
| UTC_E_GETFILE_EXTERNAL_PATH_NOT_APPROVED | UTC_E_CERT_REV_FAILED |
UTC_E_TRY_GET_SCENARIO_TIMEOUT_EXCEEDED
Map the code to the scenario graph: scenario-definition query
When UTC_E_TRY_GET_SCENARIO_TIMEOUT_EXCEEDED (0x87C5103E) is returned, the producing layer is Universal Telemetry Client API coordination. A reliable investigation preserves the producing action before any cleanup runs. The rejected object or state is scenario-definition query, and the specific condition is that the lookup/query operation exceeded its caller-specified maximum time before returning a definition. Keep this first HRESULT even if a later service call reports another error.
UTC API requests may cross an RPC boundary and complete asynchronously even when exposed through a synchronous wrapper. Request submission, waiting, cancellation and result retrieval are separate stages, so one request ID should tie the evidence together.
Data needed for triage
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | scenario-definition query |
| Producing layer | Universal Telemetry Client API coordination |
| Do not confuse with | UTC_E_RPC_TIMEOUT is a general API-manager RPC timeout and may affect operations other than scenario lookup |
| Evidence to collect | scenario ID, timeout value, configuration-store latency, service load, request ID and cancellation result |
| Narrow comparison | query a known cached scenario with the same timeout, then the failing definition |
Reproduce without collateral changes
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: scenario ID, timeout value, configuration-store latency, service load, request ID and cancellation result.
- Use a passing control on the same Windows build, then query a known cached scenario with the same timeout, then the failing definition.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_RPC_TIMEOUT — is a general API-manager RPC timeout and may affect operations other than scenario lookup.
Request-lifetime note
Assign a correlation identifier before submission and retain it through wait, callback, cancellation and result retrieval. This prevents a late completion from being mistaken for the response to a newer request.
Fix the contract
Remove store/lock contention or use a justified bounded timeout; keep cancellation correct.
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for Universal Telemetry Client API coordination while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis
- Microsoft: Remote Procedure Call documentation
- Microsoft: WaitForSingleObject
Looking for a different code? Search another status or error code.