Every status websocket update (triggered by an importStatus change of any configured engine) currently causes a REST API call to the engine on `/version` to verify the engine is available. This call is triggered by every status update connection and thus causes an unnecessary amount of such requests only limited by the number of allowed websocket connections import.data.decision-instance.maxPageSize. See linked support ticket.
- the engine status is either updated in regular intervals or indirectly through the import activity and stored
- the status websocket update relies on the stored status rather than triggering individual checks for every single connection