After an error closes the websocket, a connection is not re-established

[boxmein]

Current behavior

In the GraphQL Subscriptions interface a WebSocket is opened for subscription traffic. However, when the WebSocket closes due to an error, it will not be re-opened.

This may lead to lost update messages as there isn't a mechanism that reopens the WebSocket.

Expected behavior

The library continues to try and re-establish the connection to the backend, until there are no more subscribers left.