2026-05-05 - WebSocket Double-Connect After Avatar Update Fixed¶
Release¶
AgileData.io - Cleaner Connections: WebSocket No Longer Reconnects Twice After Profile Updates
Updating your profile avatar was triggering the WebSocket connection to reconnect twice in quick succession. This has been fixed — profile updates no longer cause unnecessary WebSocket reconnections.
The root cause was that avatar images were being converted to blob URLs on the client, and the change in avatar URL was being interpreted as a meaningful state change that required a new WebSocket connection. Two reconnection events were firing back-to-back before the connection stabilised. The fix correctly identifies avatar URL changes as a cosmetic update that does not require a new WebSocket session.
What was happening:
Updating your profile picture caused the WebSocket to disconnect and reconnect twice
During the reconnection window, real-time notifications and updates were briefly unavailable
The issue occurred every time an avatar was loaded or updated, not just the first time
What this means for you:
Profile picture updates no longer interrupt your live connection to AgileData
Real-time notifications remain uninterrupted when you make profile changes
Fewer unnecessary network requests and reconnection events during normal use
Last Refreshed¶
Doc Refreshed: 2026-05-05