Repository navigation
Fix participant system messages with client clock skew - #6085
Merged
mgamis-msft merged 2 commits intoOct 9, 2026
Merged
Conversation
mgamis-msft
force-pushed
the
mgamis/fix-latent-clock-skew-for-system-messages
branch
from
October 7, 2026 18:10
3b6fe7f to
78c6007
Compare
Contributor
📦 CallWithChat bundle size
Total change: +1436.6 KB |
Contributor
📦 Chat bundle size
Total change: -11.2 KB ⬇️ |
Contributor
📦 Calling bundle size
Total change: +1447.7 KB |
Contributor
@azure/communication-react jest test coverage for stable.
|
Contributor
@azure/communication-react jest test coverage for beta.
|
mgamis-msft
enabled auto-merge (squash)
October 7, 2026 19:05
prabhjot-msft
approved these changes
Oct 9, 2026
mgamis-msft
deleted the
mgamis/fix-latent-clock-skew-for-system-messages
branch
October 9, 2026 22:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Fixes missing participant join and leave system messages when the client device clock differs from the ACS SDK clock. The recovery query now uses the participant event timestamp instead of client device time.
Why
Client devices with clock skew are not seeing participant joined system message in the chat thread
Related to this IcM https://portal.microsofticm.com/imp/v5/incidents/details/21000001135358/summary about missing typing indicators also caused by clock skew
How Tested
Tested in locally by applying a 45 second clock skew to receiving device
Before with release validation app when remote participant joins chat thread:


After with local deploy when remote participant joins chat thread:
Process & policy checklist
Is this a breaking change?