80022: Connection not found

A request referred to a connection that the server could not find, so the exchange could not continue and the client is signaled to reconnect. This is a lookup failure, not a loss of message continuity.

What you should do

Usually nothing. This is a non-fatal error that the SDK handles by re-establishing the connection, so no intervention is normally needed. Investigate only if it surfaces to your application repeatedly.

Why it happens

A request reached a server that wasn't handling the connection it referred to, so the connection couldn't be found. This is typically a transient routing effect, for example after disruption on one of Ably's servers, and it resolves once the client reconnects.

What you'll see

The error is reported with code 80022 and HTTP status 410. The message is typically Unable to find connection.