Suggest an Idea

[vegard_bakke]

Could Qlik Sense please attempt to reconnect to the websocket when the connection is lost?

When users on laptops disconnect from their docking station and go to wifi (or vica versa), all websockets will be dropped.

But other applications try calling home to reconnect. Qlik Sense doesn't, and this leads to much frustration. 

This also applies when connecting to some VPNs, flaky wifi signals, etc. 

[vegard_bakke]

Many network boxes kill idle websockets. 

Azure Gateway defaults to killing any idle websockets after 4 minutes.
Can be configured to a maximim of 30 minutes.
https://azure.microsoft.com/en-us/blog/new-configurable-idle-timeout-for-azure-load-balancer/

If Qlik Server closed the connection with 'OnSessionTimedOut', keep the current behaviour.

But if the connection is just dropped, please redial.  And when redialing, consider adding a console message: 'Webcosket connection lost. Reconnecting. (Happend 04:00 minutes since the previous lost connection.)' OR at least state the time when it happened.

In a complex network architecture, with multiple clouds, IT centers etc, timing the connection drop is the only information that can help you find the source.
If it always cuts out after 4 minutes, you start looking at the Azure Gateway.
If it always cuts after 2 minutes, you look in IBM WebSeal.
If it varies, it is not a timeout setting, but a flaky network.  Happy hunting. (But at least you know it is not a timeout setting, so you can skip investigating those.)

[ToniKautto]

Qlik Sense Enterprise SaaS has a 30 second TCP keep-alive enabled for the WebSocket connection.
This means that an ideal session will not be closed prematurely, with the assumption that the TCP keep-alive packages are honored by all network devices in the routed path. 

[vegard_bakke]

And if I take my laptop out of the docking station....?

or connect to a VPN that reroutes the traffic...?

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.