Creating a Websocket may fail due to network problems or outdated network components. This sets how many seconds logic will wait before abandoning the websocket creation.
Introduced in 2024, this setting can help in tuning how a user experiences temporary network disruptions / degradation.
Since the websocket creation process involves some protocol "tricks" where an HTTP request is upgraded from a single connection to a persistent, full duplex link, during network degradation a websocket creation will frequently time-out. This is when the upgrade is essentially lost and there is not a built-in retry like there is for typical HTTP requests.
Prior to the version introducing this, the timeout was 30 seconds, which can cause very slow recovery.
Essentially, pairing this with a lower number of WebSocket Max Retries will speed logic to revert to AJAX web socket calls, which are more resilient than a websocket create in a degraded network. With the new recovery logic introduced with this setting, once the network health is restored, the connection will be re-upgraded to a websocket to restore performance, particularly for ASCII protocols like VTxxx.
Default: 10 seconds
