| Previous | Next |
| ERROR_PORT_UNREACHABLE | ERROR_CONNECTION_ABORTED |
ERROR_REQUEST_ABORTED
The request was aborted before it completed.
ERROR_REQUEST_ABORTED is Win32 error 1235 (0x4D3). It is a broad request-lifecycle result. A lower layer, local controller, connection teardown, service shutdown, or cancellation path ended the request, but the code alone does not identify the initiator.
Reconstruct the abort chain
- request ID and parent operation
- component that first issued cancel, close, reset, or shutdown
- transport connection state immediately before the abort
- deadline and timeout values at every layer
- bytes or logical stages completed before termination
- the original error that caused a batch or session to be torn down
Do not discard the initiating failure
One failed request can cause a connection manager to abort many dependent requests. If every dependent operation logs only 1235, the root cause is buried under secondary noise. Preserve the first failure and link subsequent aborts to it with a correlation or session identifier.
Data consistency
Determine whether the remote side or persistent subsystem may have processed the request despite the local abort. Reads are usually safe to repeat, but writes, payments, account changes, and job submissions require an idempotency key or a status query before retry. “No response received” is not proof that no side effect occurred.
Retry decision
Retry only after classifying the cause. A new connection may recover from transient transport teardown; a service shutdown should wait for restart; explicit cancellation should not be overridden. Apply bounded backoff and preserve the original request identity when the protocol supports deduplication.
Difference from cancellation and connection abort
ERROR_CANCELLED explicitly describes a user-canceled operation. ERROR_CONNECTION_ABORTED identifies a network connection aborted by the local system. Error 1235 applies to the request and can be a consequence of either connection loss or higher-level cancellation.
Developer recommendations
- make abort reasons structured rather than plain text
- separate primary failures from dependent cancellations
- define commit points for multi-stage operations
- make cleanup safe if completion races with abort
- test service stop, timeout, disconnect, and duplicate retry
Example
A client sends several operations over one authenticated session. Token renewal fails, so the session manager closes the transport and pending calls receive 1235. Telemetry links them to the renewal failure; read requests reconnect and retry, while a submitted write first queries its idempotency key to avoid duplication.
References
- Microsoft: System Error Codes (1000–1299)
- Microsoft: CancelIoEx function
- Microsoft: Canceling Pending I/O Operations
Looking for a different code? Search another status or error code.