In QlikSense the session inactivity timeout counter is restarted if a reload on the app is performed, so if an app is reloaded more often than the defined inactivity timeout, the end user session never closes (unless they close their browser themselves). This was not the case with QlikView and it has big impact on resource consumption(end user leaves his browser tab opened and the server consumes RAM and CPU for them even if they don't use the report anymore).
