| Previous | Next |
| STATUS_LOCAL_DISCONNECT | STATUS_REMOTE_RESOURCES |
STATUS_REMOTE_DISCONNECT
STATUS_REMOTE_DISCONNECT means that the remote side closed the transport connection. Its operational consequence is that outstanding requests may have an unknown outcome. The status does not prove a local timeout; it distinguishes a closure originating at the remote transport side from a locally detected expiry.
How to narrow it down
Correlate the client timestamp with server logs, load balancer events, service restarts, failover and network captures. A remote close can be deliberate, caused by resource pressure, protocol/security enforcement or a server fault. The first diagnostic task is to identify the owner of the close, not to replay traffic immediately.
For write, create and delete operations, establish a post-reconnect verification rule. For example, use a request identifier or remote object version to decide whether the operation needs no replay, a safe retry or human review.
Evidence that matters
- Collect server and intermediate-device events around the exact close time.
- Separate remote close from local request timeout using trace ordering.
- Verify the result of outstanding state-changing operations after reconnect.
References
Looking for a different code? Search another status or error code.