2026-06-15 - WebSocket Token and Session Expiry Fixes¶
Release¶
AgileData.io - Stable Connections: WebSocket Authentication and Session Expiry Corrected
Two related fixes improve the reliability of live data connections and session handling in the application.
The first fix addresses an issue where fetching the WebSocket token was incorrectly triggering a CORS-related login redirect. The token fetch is a background operation and should never cause the user to be redirected — this has been corrected so WebSocket connections establish cleanly without interrupting the user’s session.
The second fix adds proper 401 (session expired) handling to the default catalog page data fetches. Previously, if your session expired while the catalog was loading its initial data, the expiry wasn’t being caught at this point — you might see an error or stale data rather than a clear re-login prompt. This is now handled correctly.
What was happening:
Fetching the WebSocket authentication token was triggering an unexpected CORS login redirect
Session expiry on initial catalog page fetches wasn’t being caught, leading to errors rather than a clean re-login prompt
What this means for you:
WebSocket connections establish cleanly without unexpected redirects
Expired sessions are caught and handled correctly when loading the catalog, giving you a clear re-login prompt
Last Refreshed¶
Doc Refreshed: 2026-06-15