fix: #36023 - Omnichannel widget fails to show new messages #36076
+9
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fix: Livechat widget can lose connectivity on websocket (issue 36023 - #36023)
We do not know any way to test the fix. It takes a very specific virtualization environment created to emulate unidirectional communications for a short period of time, similar to what cell phones can experience in fringe coverage. See bug 36023 for the way we created this environment in Hyper-V. While we do not absolutely know that this is what causes our 0.019% of cases where the visitor has expressed the inability to see the messages from the agent, we do know that this is a potential cause. We also know that the proposed fix eliminates this cause.
Proposed changes (including videos or screenshots)
This changes ensures that a client based failure on the ddp-client websocket causes a reconnection of the websocket used for server based events, including new message events.
Issue(s)
#36023
Steps to test or reproduce
Further comments