When something goes wrong with the underlying websocket, timeout, SSL issue, etc. the websocket API logs the error, but then does nothing to notify the caller of the API that something has gone wrong. Making it impossible to handle errors and reset/restart the websocket. Is there something I am missing that handles this in the API? Thanks!
When something goes wrong with the underlying websocket, timeout, SSL issue, etc. the websocket API logs the error, but then does nothing to notify the caller of the API that something has gone wrong. Making it impossible to handle errors and reset/restart the websocket. Is there something I am missing that handles this in the API? Thanks!