Oct 09 2022 01:50 AM
Oct 09 2022 01:50 AM
We've begun using the new "Shared Channels" extensively inside our org. However we've noticed a major bug which makes it impossible to use this new feature before it has been fixed:
When we create a shared channel and share it with another team, then the members of each team only sees some messages and it's completely random who sees what. The messages are simply not showing up for some users while they do for others. This is only a problem with the Windows client. It works fine in the web version and on mobile (IOS).
We're running Microsoft Teams version 1.5.00.21668 64-bit. We also tried upgrading a few user to latest preview build but this did not fix the issue.
I am member of team A. I create a shared channel and shares it with the owner of team B. The owner accepts the invite and i accept the placement of the channel at team B. All is good. The channel shows up both in my team A and in team B.
However, if I write a new thread, sometimes it'll show for all members of team B and sometimes only for some members. It will always make the channel name bold as if there is a new unread message but if the user clicks on the channel then there is nothing new. If they look in the mobile app or the web version they can see the message.
If they then write a response on their phone, it'll sometimes show up on the Windows version but as a new thread and not a response.
This makes the new shared channels unreliable as one can't guarantee that other members actually gets your message.
Oct 13 2022 04:30 AM
Oct 15 2022 12:56 AM
Yes I got a response asking me to clear the Teams cache through these steps:
If Teams and outlook app is still running, right-click the Teams icon in the dock, and then select Quit, or press Command (⌘)-Q and close outlook app.
In the Finder, open the /Applications/Utilities folder, and then double-click Terminal.
Enter the following command, and then press Return:
rm -r ~/Library/Application\ Support/Microsoft/Teams
This does indeed fix the problem for PAST missing messages. We're currently investigating/observing if it also fixes the problem for future messages (messages being sent after the cache clearing).
Oct 20 2022 01:17 AM
Nov 09 2022 08:42 AM
Nov 09 2022 11:14 AM
@Nicki_GreeneNo permanent fix. Only clearing the cache will solve the issue temporary. Right now I'm not in the mood to contact the most useless MS Support (Teams). So many issues and escalations from past cases...
Nov 16 2022 06:18 AM
Dec 13 2022 05:09 AM
Dec 15 2022 11:06 PM