- Ably FAQs
- Realtime API and client libraries
- Connections
-
Account billing and packages
-
General
-
Realtime API and client libraries
-
Troubleshooting
-
Channels
-
REST API and client libraries
-
Ably error codes
-
Account and app setup and configuration
-
Ably architecture, transports, and security
-
Performance and Redundancy
-
Push Notifications
-
Integrations
-
Migrating to Ably from an existing service
Why is my Ably realtime connection sometimes disconnecting and reconnecting?
The Ably system can validly drop client connections at any point, and will do for a variety of reasons, such as our internal autoscaling, or automatic active connection rebalancing, or a deployment of a service the client is connected to or through.
When this happens, the Ably SDK will immediately automatically reconnect, and using our connection state recovery functionality, will resume with full connection continuity (no missed messages).
This will typically be exposed in the SDK as a connection state change event from `connected` to `connecting`, typically with code=80003 (though that may vary between SDKs), shortly followed by another state change event back to `connected` once it reconnects. The full sequence will generally be complete within a couple hundred milliseconds.