80003: Connection disconnected

The connection to Ably was dropped. This is a normal, usually brief interruption, such as a network change or Ably cycling the connection, rather than a deliberate close, and the connection is expected to be re-established.

What you should do

Usually nothing. Disconnection is a routine part of maintaining a realtime connection, and the Ably SDK handles it for you: it moves the connection to the disconnected state, retries automatically, and returns to connected, resuming where it left off. A 80003 that clears on its own is expected, not a fault.

Act only if the connection does not return, or disconnects often enough to disrupt your application. Frequent disconnections usually point to the network path between the client and Ably, such as the client's own connectivity, or a proxy, firewall, or load balancer that drops long-lived connections; check there first.

Why it happens

The transport carrying the connection was lost, commonly a network change or interruption on the client side, or Ably closing the transport so the client reconnects. It is not an authentication failure or a deliberate close by your application, both of which are reported with their own codes. While disconnected, the SDK keeps any messages you publish and sends them once it reconnects.

What you'll see

This code is not delivered as a server response in the usual case; it is the reason attached to the connection's disconnected state. The connection enters the disconnected state, carrying reason code 80003 with the message Connection disconnected, and returns to connected once the transport is re-established.