Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
SKai
Contributor II
Contributor II

Qlik Sense sessions timing out too quickly during scripting/visualization

Hi everyone,

SKai_0-1789444240231.png

Recently I’ve been facing an issue in Qlik Sense where the application keeps offloading while I’m working on scripting or visualizations in a tab. When this happens, all other open tabs need to refresh after not more than 3–5 minutes.

By default, Qlik Sense should allow 30 minutes of user inactivity before an idle session times out and shows the error/reconnection message. However, I’m now seeing the inactivity message after less than 5 minutes, even while actively working.

This behavior is making progress very slow and disrupting my workflow. Previously, the issue only occurred after a longer period of inactivity, but now it happens almost immediately. And, I could reload data without losing activity in other tabs. Now, the moment a reload starts, every other tab becomes inactive right away.

Has anyone else experienced this sudden change in session timeout behavior? Could this be related to server configuration, resource limits, or recent updates? Any guidance on how to troubleshoot or fix this would be greatly appreciated.

Thanks in advance for everyone's help!

Labels (4)
2 Replies
vighnesh_gawad
Partner - Creator II
Partner - Creator II

Hi @SKai ,

Check out below support article. You can try solution given in article. 

https://community.qlik.com/t5/Official-Support-Articles/Hub-access-times-out-with-Error-Connection-l... 

Regards, Vighnesh Gawad
Connect with me on vighneshgawad.com | LinkedIn | GitHub
ift_isabelle
Partner - Creator III
Partner - Creator III

It is tuesday = release day in Qlik Cloud.

We experience hick ups weekly at tuesdays. 
If the problem is still there tomorrow, first try a different network and otherwise log a ticket at Qlik.