User getting logged out of Qlik Sense while working with the Data Load Editor

A user may get automatically logged out from Qlik Sense while working with the data load editor, this may cause the user to lose the scripting work and code changes that they have been doing.

When accessing the Qlik Sense server via various networks or locations, the WebSocket communication may get blocked, failed or timed out caused by certain device connection idle settings within a specific network. For example accessing Qlik Sense server from an office works but accessing from home fails.

When accessing from home the user may be connecting via their ISP to their organisation private network then to the Qlik Sense server.

The issue  could be within a device within the ISP network that is causing the websocket communication to fail. 

When users are working from the office there may be no issues so the problem may clearly be within the network that is outside the office.

As a result this can cause the system to detect no user activity when working with the data load editor and result in sessions expiry and user to get automatically logged out.



 

See Enabling TCP Keep Alive Functionality In Qlik Sense for a possible workaround to introduce a keepalive. Available from June 2018.