Jan 11 2019 09:47 AM
Jan 11 2019 09:47 AM
We are seeing this on root conversations in some of our channels. We thought it was someone in our group but we verbally confirmed no one deleted these Conversations. The replies however are not deleted. My CIO noticed that this is also happening on another Teams Channel he was invited to to at another Firm. So its not just us it seems. Anyone have a clue? I tried Audit logs but they on track Team and Channel deletions.
Jan 11 2019 10:16 AM
Jan 11 2019 11:17 AM
Jan 15 2019 05:08 PM
We're seeing this also noticed today. In many Teams and channels. Seems random where the root message of the conversation moved to the replies. It's confusing because the message says "This message has been deleted", but when we open replies there's the root message so nothing is really deleted. I opened a case with Microsoft.
Jan 18 2019 02:24 PM
I have a user experiencing this behavior as well. Going to initiate a ticket Monday if it they still see it. Otherwise if anyone else on the thread has already started an incident with Microsoft, I would definitely be interested in what they've said and what has been done so far for debugging.
To add to the description, when I look at the post I don't see the root message as "This message has been deleted" I see the first reply as the root... on a discussion session started 11/27/2018.
Jan 24 2019 07:07 AM
I found a temp fix but this should not be marked as solution. MS gave me all the cache folders for Teams. We wiped out the contents of the folders and that fixed the issue for the user. I dont think wiping cache should be the fix. I think MS needs to address. I also have a ticket open with them. I'm trying to get a KB that mentions this issue or something from MS stating they know about this issue. I also am trying to get an ETA for some kind of fix which i know is pointless but I i have to ask, here are the folders that need to be emptied.
Jan 24 2019 08:49 AM
Jan 24 2019 10:26 AM
Well For us we have ADFS in house so SSO is in play. I get having to wipe cache but man I shouldnt have to do this as many times as I have.
Jan 24 2019 10:30 AM
Jan 24 2019 10:37 AM
Mar 06 2019 05:41 AM
Mar 06 2019 05:54 AM
@Hyper-X Yes, they did - said it was a minor visual bug and it would be addressed in a future update. Not sure if they need much data about it still but I'm sure they are tracking the number of people experiencing the issue. If people have access to the O365 Admin Center for toggling setting in at least one of the products... the experience opening a ticket was pretty good for all of the times I've done it so far. Submit an incident, wait and someone from Microsoft calls you. Gather up the data they need to use to troubleshoot/debug and if they have to go back to the product team they will keep you in the loop with the status.
Mar 22 2019 10:19 AM
We noticed this bug as well and it seems, at least in our environment, it's only messages that have tab conversations related to them. They posted a doc and then viewed it and started a conversation on it. It is still affecting us at the moment, so not sure if someone could share a case number so we can keep an eye on it. @Christian Taveras