[BUG][4.2] Persitent websocket callback lost updates.

[T4rk1n]

When a websocket disconnect on the frontend by cause of inactivity for example, the websocket is reconnect when any other callback happen. But if you have a persistent websocket callback running in the background, it will not be able to send set_props or get_props request and the is_shutdown is not changed since it was reconnected.

This suggest the queue handling is lost when the websocket reconnect.