| Previous | Next |
| WS_E_ENDPOINT_ACTION_NOT_SUPPORTED | WS_E_ENDPOINT_FAULT_RECEIVED |
WS_E_ENDPOINT_TOO_BUSY
WS_E_ENDPOINT_TOO_BUSY is a Windows Web Services API HRESULT. It means that the remote endpoint could not accept or process the request because it is overloaded or has exhausted a service-side capacity limit.
What to check for WS_E_ENDPOINT_TOO_BUSY
- Check server concurrency, queues, CPU, memory, downstream dependencies and throttling policy.
- Honor retry-after or service-specific backoff guidance when it is available.
- Use exponential backoff with jitter and avoid synchronized retries that increase the overload.
Diagnostic interpretation
This result has the HRESULT value 0x803D0012. AllStat records the condition as “The remote endpoint is unable to process the request due to being overloaded.”.
Evidence to capture
- Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions this result or the ws / endpoint / too / busy operation.
- check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.
Retry and recovery
” has changed.
Looking for a different code? Search another status or error code.