Any interruption in Internet connectivity (caused by Qlik, customer environment, or third parties), a deployment in QCS or other QCS incident could cause a disconnect.
If the time a Gateway is Disconnected is short, is unlikely to have reloads affected. For some customers with a high volume where seconds count, reloads might fail. Under those circumstances it is suggested to use some kind of application-level resiliency strategy like retries via QAA, API's, at least for the Direct Access Gateway.
The DirectAccess.log shows:
41 2024-04-21 04:17:08 [Service ] [ERROR] Connection failed
System.Net.WebSockets.WebSocketException (0x80004005): The remote party closed the WebSocket connection without completing the close handshake.
Resolution
Make sure the Direct Access Gateway was configured following recommendations documented in our help site.
Install at least Direct Access Gateway 1.6.6 or later.
Cause
R&D indicates that the low-level WS disconnects in the DirectAccessAgent.log are expected. We should expect to see at least 1-2 per day on average
Related Content
Qlik Data Gateway - Direct Access. Reloads failing intermittently
Qlik Application Automation: How to automatically rerun a failed automation
Internal Investigation ID(s)
QB-25723
Environment
- Data Gateway Direct Access
