https://community.qlik.com/t5/App-Development/No-timeout-for-some-while-timeout-for-other-apps-users/m-p/1657914#M49251 <P>Hi all,</P><P>I'm hoping to do this:</P><P>Application A doesn't time out because it goes onto a big screen.</P><P>The rest of the applications, different user from A, continue to session time-out as per default.</P><P>&nbsp;</P><P>Thank you!</P><P>Regards,</P><P>Alloy</P> Sat, 16 Nov 2024 19:27:12 GMT DoesitMatter 2024-11-16T19:27:12Z https://community.qlik.com/t5/App-Development/No-timeout-for-some-while-timeout-for-other-apps-users/m-p/1657914#M49251 <P>Hi all,</P><P>I'm hoping to do this:</P><P>Application A doesn't time out because it goes onto a big screen.</P><P>The rest of the applications, different user from A, continue to session time-out as per default.</P><P>&nbsp;</P><P>Thank you!</P><P>Regards,</P><P>Alloy</P> Sat, 16 Nov 2024 19:27:12 GMT https://community.qlik.com/t5/App-Development/No-timeout-for-some-while-timeout-for-other-apps-users/m-p/1657914#M49251 DoesitMatter 2024-11-16T19:27:12Z https://community.qlik.com/t5/App-Development/No-timeout-for-some-while-timeout-for-other-apps-users/m-p/1658093#M49277 The default behavior for a sense server would only allow this if you send users to different virtual proxies. The timeout is controlled by VP. Otherwise, you would need to have Application A be exposed by mashup and have javascript reloading it quietly in the background to keep it acctive since the timeout is based on client side actions. Mon, 16 Dec 2019 14:20:31 GMT https://community.qlik.com/t5/App-Development/No-timeout-for-some-while-timeout-for-other-apps-users/m-p/1658093#M49277 andoryuu 2019-12-16T14:20:31Z