The users see timeouts of their session on the HUB or while idling in a QlikSense App, requiring a reconnect, even though the QlikSense Proxy has been configured with the correct timeout values.
Possible on-screen messages when triggered by Sense:
Possible on-screen message when triggered by a network disconnect/ 3rd party timeout:
QlikSense is not the only system that can affect timeouts. The following components can interfere with configuration done on the Sense side:
- Browser Timeouts (see Browser Timeout)
- Firewall Disconnects (consult with the local network team for information logged)
- Mobile Devices (iOS) closing network connection when losing focus/locking screen
- Proxy Timeouts (3rd Party software used for Internet Access - consult with the local network team)
- Web Shields (such as Avast Antivirus)
This is not a comprehensive list. Any active network component involved between the end user and server can impact session timeouts.
How to verify if a 3rd party network component is responsible for a timeout:
An end user connecting through a VPN connection experiences a timeout of 3 minutes, but the Qlik Sense Session timeout is set to the default 30 minutes.Test:
Connect directly from the Qlik Sense proxy node to the local hub. Ensure that no 3rd party proxy is being used and that browser timeouts are correctly configured. Test if the session is still terminated too early. If it doesn't, the network components between end user and server need to be investigated.
How to verify if the Session Timeout setting is correctly applied:
An end user connecting through a VPN connection experiences a timeout of 3 minutes, but the Qlik Sense Session timeout is set to 5 minutes. It is not clear if the timeout of 5 minutes is correctly accepted.Test:
Change the timeout in the Qlik Sense Virtual proxy to a shorter time, for example 1 minute. If the session times out after 1 minute, then the longer timeout of 5 minutes has also been correctly applied.