| 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.
Diagnostic discriminator: Use server capacity and throttling evidence to distinguish overload from an unavailable or invalid endpoint. If the same request succeeds after queue depth or concurrency falls, the code represents service-side pressure rather than a contract error. Preserve any retry-after guidance and avoid synchronized retries that can extend the overload condition.
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.
Looking for a different code? Search another status or error code.
