Qlik Sense Session Inactivity Timeout and Keep Alive settings

[Zareh_T]

Qlik Sense allows for three settings that may influence the perceived connection and session timeout period. These are the "Session Inactivity Timeout", "Keep-Alive Timeout", and "TCP Websocket keep-alive"  settings. 

Note: Adjusting the below settings can help when working with slow internet connectivity or wanting to extend the session inactivity. However, session disconnect issues can be caused by other network connectivity issues and by system resource shortage as well and may require additional troubleshooting.  See Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

 

1.  The connection "Keep Alive" setting

This is the maximum timeout for a single HTTP request. The default value is 10 seconds. During the defined keep alive timeout value, the connection between end user and Qlik Sense will remain open.

It serves as protection against denial-of-service attacks. That is, if an ongoing request exceeds this period, Qlik Sense proxy will close the connection.

Increase this value if your users work over slow connections and experience closed connections for which no other workaround has been found. Make sure to take the mentioned DoS consideration above into account. 


 

2.  The "Session Inactivity Timeout"

This is the browser authentication session time out ( 30 minutes by default set under Virtual Proxy in QMC ). This sets a cookie on the client machine with the name X-Qlik-Session. This cookie can be traced in Fiddler or Developer tools under the  header tab. 

If the session cookie header value does not get passed, is destroyed, or modified between the end user client and the Qlik Sense server while 'in-flight' the user session is terminated and the user is logged out.

By default, it will be destroyed after 30 minutes of inactivity or when the browser is closed.

3. TCP Websocket keep-alive

This is another setting that may help keep the connection open in certain environments. See Enabling TCP Keep Alive Functionality In Qlik Sense. Note that customers who don't experience any issues with web sockets terminated by the network due to inactive SHOULD NOT switch this feature ON since it may potentially cause Qlik Sense to send unnecessary traffic on the network towards the client.

Related Content:

• Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly 

Environment:

• Qlik Sense Enterprise on Windows, all versions

[KeyReaL]

What maximum parameter can be installed in the "Session Inactivity Timeout"?

[Sonja_Bauernfeind]

Hello @KeyReaL 

We are not aware of there being a limit. 

All the best,
Sonja 

[SGMarquez]

In our case with Azure, although we have 30 minutes, after two minutes the connection is lost

[Sonja_Bauernfeind]

Hello @SGMarquez 

The timeouts are not only affected by what is set in Qlik Sense. Third-party software can terminate sessions as well. See Hub access times out with: Error Connection lost. Make sure that Qlik Sense is running properly on guidance around this.

All the best,
Sonja 

[SGMarquez]

thanks, we will do those test

[woutermak]

Thanks, good post

[SGMarquez]

la base del problema fue que hay que reducir el tiempo en Qlik en vez de aumentarlo. La verdad que no conozco el motivo de esto pero así ya funcionaba (en cuanto lo aumentabamos dejaba de funcionar).

[michaelp]

Hello,

Is it possible to set the Session Inactivity Timeout for one user? For example I want a dashboard in Qlik Sense that can be viewed on one monitor where the users can see stats throughout the day. 

Thank You so much,

Michael

[Sonja_Bauernfeind]

This setting cannot be adjusted individually for users. 

You need to ensure the dashboard is periodically refreshed if you do not wish to expand the timeout further.

All the best,
Sonja 

[michaelp]

Hi Sonja,

Thanks so much for the reply Sonja. What do you mean by "dashboard is periodically refreshed"?  My goal is to show Measures on a big monitor with no human intervention in an emergency room setting 24/7. The app or dashboard is on a big monitor for ER staff to see.  It should almost be on real time. It will show the number of patients, the wait time, it should be less than 20 min., the time when patients enter the Door to Bed or provider consult. etc. My 1st. process is to load the data from the DB by executing a stored procedure in Qlik. 2nd process is to load the data to the app or dashboard. The 1st and 2nd process is scheduled in the Qlik Console Task. That's the backend process. No issues with that process. The issue is when the logged in user is automatically logged out when the time out ends in the proxy.  It's currently set to 30 min. To circumvent the auto logged out after 30 minutes, I was going to run a script in chrome or Edge/IE browser to refresh every 2 or 5 min so that the session doesn't close or logs the user out. Is there a better solution? Or is my process going to work?

Thanks so much.