2026-06-29 - WebSocket Falls Back to API Payload When Area Tiles Unavailable¶
Release¶
AgileData.io - Always Up to Date: Catalog Now Falls Back to API Data When WebSocket Tiles Are Missing
The catalog uses WebSocket messages to receive live tile updates for specific catalog areas. In some cases, a WebSocket payload wouldn’t include area-specific tile data — for example, when the WebSocket message was a general update rather than an area-targeted one. Previously this could leave the catalog displaying stale or missing tile data.
AgileData now falls back to the standard API payload in these cases. If the WebSocket message doesn’t include area-specific tiles, the catalog retrieves the latest data from the API instead, ensuring the catalog always shows current information.
What was happening:
When a WebSocket payload didn’t include area-specific tile data, the catalog could display stale content
No fallback existed for WebSocket messages that lacked targeted tile updates
What this means for you:
The catalog always shows current tile data, even when WebSocket updates are partial or general
More reliable catalog display across different update scenarios
Last Refreshed¶
Doc Refreshed: 2026-06-29