Oct 26 2021 12:07 AM
When one user sends Teams chat messages to another user , these messages are immediately marked as read to the sender even when the receiver hasn't read them. Teams Cache has been deleted already, nothing suspicious in the settings of both users. It's only between these two users and only one way. This happens also via the Teams Mobile App.
Oct 26 2021 04:06 AM
Dec 06 2021 11:49 AM
Dec 07 2021 05:12 AM
Did you find out anything more about this? I am experiencing the same thing with one user interacting with one other user. Thx!! @Josh DeWitt
Jan 20 2022 07:26 AM
@InnocentTugume I am also having this issue. Some chats randomly jump to read and messages get missed.
Jan 26 2022 07:21 PM
Feb 02 2022 08:35 PM
Feb 14 2022 11:20 AM
@InnocentTugume
This has been happening to me for awhile now, and it's only one user. I've tried literally EVERYTHING to fix this but no matter what I do, messages from him are White 'New' Text for a split second, then go to the read 'grey' with no notification. When I have 'read receipts' turned on, he says that it appears that I read the message immediately. I've often missed messages from him because of this bug and it's really affecting my communication with him, plus giving the impression that I've received the information but am ignoring it.
I've tried:
-Clearing cache on every device I have teams installed
-Uninstalling/Reinstalling on every device
-Uninstalling every other device I have teams installed, leaving only my work PC
-Changing 'Read Receipts' and other notification settings
-Muting/unmuting, marking as read, pinning, unpinning the user I'm having issue with
-Using the web client. It still happens on the web client!
I wish there was an update for this problem, it's driving me insane and making my coworker think that I'm intentionally ignoring him :(
Mar 29 2022 09:24 AM
I just ran into this problem this morning and found a fix. If you're not in IT, have your IT log into the M365 admin portal and and them click on the Sign out of all sessions link for the user who is affected by this issue.
May 26 2022 11:46 PM