Sometimes, the WebSocket connection between the delivery service and the web client does not function properly. As a result, messages can only be fetched from the delivery service after a page reload, instead of being instantly delivered via WebSocket.
The cause of this issue is still unclear, but we need to monitor it closely.
Steps to (occasionally) reproduce the issue:
- Open DM3 in two separate sessions.
- Send messages back and forth.
- One client can receive messages, while the other cannot.
Sometimes, the WebSocket connection between the delivery service and the web client does not function properly. As a result, messages can only be fetched from the delivery service after a page reload, instead of being instantly delivered via WebSocket.
The cause of this issue is still unclear, but we need to monitor it closely.
Steps to (occasionally) reproduce the issue: