Home

Teams : This message has been deleted.

%3CLINGO-SUB%20id%3D%22lingo-sub-392147%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-392147%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306338%22%20target%3D%22_blank%22%3E%40owtucker%3C%2FA%3E%26nbsp%3B%3CSPAN%3ETicket%20%2312790064%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382788%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382788%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20noticed%20this%20bug%20as%20well%20and%20it%20seems%2C%20at%20least%20in%20our%20environment%2C%20it's%20only%20messages%20that%20have%20tab%20conversations%20related%20to%20them.%20They%20posted%20a%20doc%20and%20then%20viewed%20it%20and%20started%20a%20conversation%20on%20it.%20It%20is%20still%20affecting%20us%20at%20the%20moment%2C%20so%20not%20sure%20if%20someone%20could%20share%20a%20case%20number%20so%20we%20can%20keep%20an%20eye%20on%20it.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-361119%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-361119%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F285173%22%20target%3D%22_blank%22%3E%40Hyper-X%3C%2FA%3E%26nbsp%3BYes%2C%20they%20did%20-%20said%20it%20was%20a%20minor%20visual%20bug%20and%20it%20would%20be%20addressed%20in%20a%20future%20update.%20Not%20sure%20if%20they%20need%20much%20data%20about%20it%20still%20but%20I'm%20sure%20they%20are%20tracking%20the%20number%20of%20people%20experiencing%20the%20issue.%20If%20people%20have%20access%20to%20the%20O365%20Admin%20Center%20for%20toggling%20setting%20in%20at%20least%20one%20of%20the%20products...%20the%20experience%20opening%20a%20ticket%20was%20pretty%20good%20for%20all%20of%20the%20times%20I've%20done%20it%20so%20far.%20Submit%20an%20incident%2C%20wait%20and%20someone%20from%20Microsoft%20calls%20you.%20Gather%20up%20the%20data%20they%20need%20to%20use%20to%20troubleshoot%2Fdebug%20and%20if%20they%20have%20to%20go%20back%20to%20the%20product%20team%20they%20will%20keep%20you%20in%20the%20loop%20with%20the%20status.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-361106%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-361106%22%20slang%3D%22en-US%22%3EI%20finally%20got%20some%20sort%20or%20answer%20on%20this%20from%20Microsoft%20via%20the%20ticket%20i%20opened.%2C....%3CBR%20%2F%3E%3CBR%20%2F%3E%EE%9D%BB%20Ricky%20(Microsoft)%3CBR%20%2F%3EMonday%2C%20March%204%2C%202019%2010%3A02%20PM%20GMT%3CBR%20%2F%3EHello%20Admin%2C%3CBR%20%2F%3E%3CBR%20%2F%3EGreetings%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20your%20reply.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20be%20glad%20to%20share%20the%20root%20cause%20of%20the%20issue%20however%20this%20is%20the%20findings%20for%20now%20and%20the%20case%20is%20still%20getting%20investigated%20by%20the%20internal%20team.%3CBR%20%2F%3E%3CBR%20%2F%3EWould%20be%20fixed%20by%20the%20end%20of%20march.%3CBR%20%2F%3E%3CBR%20%2F%3EAfter%20investigation%2C%20we%20found%20out%20the%20alerted%20message%20is%20marked%20as%20deleted%20in%20local%20Teams%20client%2C%20but%20after%20sync%20with%20Teams%20server%2C%20the%20message%20is%20recovered%2C%20and%20deleted%20flag%20disappears.%20Seems%20like%20there%20is%20a%20sync%20issue%20between%20Teams%20client%20Local%20Cache%20and%20Teams%20server.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20you%20have%20any%20issue%20please%20feel%20free%20to%20contact%20us%2C%20I%20will%20be%20more%20than%20happy%20to%20assist%20you.%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20contacting%20Microsoft%20Support.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20Regards%2C%3CBR%20%2F%3ERicky%20Dhiman%3CBR%20%2F%3EMicrosoft%20O365%20Support%20Team%3CBR%20%2F%3EWorking%20Hours%20%3A-%20Monday%20to%20Friday%2008%3A00%20AM%20to%2005%3A30%20PM%20EST%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-360721%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-360721%22%20slang%3D%22en-US%22%3E%3CP%3ELogging%20out%2Flogging%20in%20to%20Teams%20resolves%20the%20problem%20for%20us%20too%2C%20but%20usually%20only%20for%20about%20a%20day%20or%20so%20before%20the%20problem%20crops%20up%20again.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228093%22%20target%3D%22_blank%22%3E%40Timothy%20Balk%3C%2FA%3E%26nbsp%3B%2C%20did%20MS%20ever%20get%20back%20to%20you%20on%20the%20ticket%20you%20opened%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-338776%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-338776%22%20slang%3D%22en-US%22%3ESeeing%20the%20same%20issue%2C%20and%20log%20out%5Cin%20resolves%20it.%20Hoping%20a%20better%20fix%20comes%20soon%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325148%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325148%22%20slang%3D%22en-US%22%3EMaybe%20scripting%20a%20deletion%20of%20the%20cache%20folders%20and%20put%20it%20as%20a%20scheduled%20task%20or%20autorun%3F%20%3Aface_with_tears_of_joy%3A%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325144%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325144%22%20slang%3D%22en-US%22%3EAgree%2C%20but%20it's%20a%20lot%20easier%20to%20click%20your%20photo%20and%20sign%20out%20than%20mess%20with%20cache%20issues%20directly%20%3Ap.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325142%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325142%22%20slang%3D%22en-US%22%3E%3CP%3EWell%20For%20us%20we%20have%20ADFS%20in%20house%20so%20SSO%20is%20in%20play.%26nbsp%3B%20I%20get%20having%20to%20wipe%20cache%20but%20man%20I%20shouldnt%20have%20to%20do%20this%20as%20many%20times%20as%20I%20have.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325084%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325084%22%20slang%3D%22en-US%22%3EIt's%20easier%20to%20just%20delete%20that%20whole%20teams%20folder%20%3AP.%20%3CBR%20%2F%3E%3CBR%20%2F%3EDid%20you%20ever%20try%20to%20do%20a%20log%20off%20and%20log%20on%3F%20That%20seems%20to%20sometimes%20clear%20out%20cache%20issues%20usually%20because%20it%20fixes%20many%20issues%20that%20quit%20%2F%20starting%20%2F%20rebooting%20will%20not%20fix%20with%20Teams.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325019%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325019%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20a%20temp%20fix%20but%20this%20should%20not%20be%20marked%20as%20solution.%26nbsp%3B%20MS%20gave%20me%20all%20the%20cache%20folders%20for%20Teams.%26nbsp%3B%20We%20wiped%20out%20the%20contents%20of%20the%20folders%20and%20that%20fixed%20the%20issue%20for%20the%20user.%26nbsp%3B%20I%20dont%20think%20wiping%20cache%20should%20be%20the%20fix.%26nbsp%3B%20I%20think%20MS%20needs%20to%20address.%26nbsp%3B%20I%20also%20have%20a%20ticket%20open%20with%20them.%26nbsp%3B%20I'm%20trying%20to%20get%20a%20KB%20that%20mentions%20this%20issue%20or%20something%20from%20MS%20stating%20they%20know%20about%20this%20issue.%26nbsp%3B%20I%20also%20am%20trying%20to%20get%20an%20ETA%20for%20some%20kind%20of%20fix%20which%20i%20know%20is%20pointless%20but%20I%20i%20have%20to%20ask%2C%20here%20are%20the%20folders%20that%20need%20to%20be%20emptied.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5Capplication%20cache%5Ccache%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5Cblob_storage%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5CCache%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5Cdatabases%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5CGPUcache%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5CIndexedDB%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5CLocal%20Storage%3C%2FP%3E%3CP%3E%25appdata%25%5CMicrosoft%5Cteams%5Ctmp%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-321635%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321635%22%20slang%3D%22en-US%22%3E%3CP%3E...%20Ticket%20opened.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-321086%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-321086%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20user%20experiencing%20this%20behavior%20as%20well.%20Going%20to%20initiate%20a%20ticket%20Monday%20if%20it%20they%20still%20see%20it.%20Otherwise%20if%20anyone%20else%20on%20the%20thread%20has%20already%20started%20an%20incident%20with%20Microsoft%2C%20I%20would%20definitely%20be%20interested%20in%20what%20they've%20said%20and%20what%20has%20been%20done%20so%20far%20for%20debugging.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20add%20to%20the%20description%2C%20when%20I%20look%20at%20the%20post%20I%20don't%20see%20the%20root%20message%20as%20%22This%20message%20has%20been%20deleted%22%20I%20see%20the%20first%20reply%20as%20the%20root...%20on%20a%20discussion%20session%20started%2011%2F27%2F2018.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-318802%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-318802%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20seeing%20this%20also%20noticed%20today.%20In%20many%20Teams%20and%20channels.%20Seems%20random%20where%20the%20root%20message%20of%20the%20conversation%20moved%20to%20the%20replies.%20It's%20confusing%20because%20the%20message%26nbsp%3Bsays%20%22This%20message%20has%20been%20deleted%22%2C%20but%20when%20we%20open%20replies%20there's%20the%20root%26nbsp%3Bmessage%20so%20nothing%20is%20really%20deleted.%20I%20opened%20a%20case%26nbsp%3Bwith%20Microsoft.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313907%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313907%22%20slang%3D%22en-US%22%3EMaybe%20creating%20a%20ticket%20with%20MS%20is%20a%20good%20idea..%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313872%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313872%22%20slang%3D%22en-US%22%3EIts%20not%20retention%20as%20that%20is%20set%20for%20a%20year%20and%20there%20are%20posts%20in%20Oct%202018%2C%201%20of%20the%205%20post%20in%20that%20month%20got%20DEL.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313870%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313870%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20conversation%20is%20in%20reference%20to%20an%20OU%20in%20AD%2C%20nothing%20sensitive%20there...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313868%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313868%22%20slang%3D%22en-US%22%3E%3CP%3EIts%20very%20random%20and%20its%20posts%20that%20do%20not%20have%20any%20kind%20of%20sensitive%20data.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313839%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313839%22%20slang%3D%22en-US%22%3EHow%20many%20messages%20are%20we%20talkin%3F%20Wondering%20if%20something%20GDPR%20%2F%20Compliance%20related%20could%20be%20stripping%20them%20out%2C%20but%20I%20don't%20think%20there%20is%20anything%20in%20just%20yet%20to%20single%20out%20individuals.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-414536%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-414536%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe're%20seeing%20this%20issue%20as%20well%2C%20on%20couple%20of%20Teams.%3C%2FP%3E%3CP%3EAny%20news%20on%20the%20ticket%20that%20was%20reported%20to%20Microsoft%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-425764%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-425764%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%40Christian%20Taveras%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%20%2C%20Since%20last%20week%2C%20my%20customer%20tenant%20also%20affected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-436108%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-436108%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EWe%20use%20Microsoft%20Teams%20as%20a%20communication%20platform%20for%20all%20staff%20at%20my%20school.%20We%20are%20noticing%20that%20conversations%20threads%20are%20getting%20deleted.%20I%20have%20asked%20around%20the%20teachers%20who%20are%20the%20'Owners'%20and%20no%20one%20is%20deleting%20them.%20Has%20anyone%20experienced%20this%20before%3F%20Thanks%20so%20much.%20I%20am%20only%20new%20to%20Teams.%20please%20help%20this%20is%20getting%20frustrating.%20I%20dont%20know%20where%20to%20go..%20All%20conversation%20threads%20have%20been%20deleted%20in%20all%20our%20channels%20back%20to%20when%20we%20started%20TEAMS%20in%20March%20HELP%20Please.%20How%20do%20I%20log%20a%20support%20ticket%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-437517%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-437517%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F319280%22%20target%3D%22_blank%22%3E%40JBeven%3C%2FA%3E%2C%20if%20you're%20having%20the%20same%20problem%20as%20others%20on%20this%20thread%2C%20signing%20out%20of%20Teams%20and%20signing%20back%20in%20seems%20to%20restore%20the%20deleted%20threads%2C%20at%20least%20temporarily.%20Do%20this%20by%20clicking%20on%20the%20user's%20photo%20in%20the%20upper%20right-hand%20corner%20of%20the%20app.%3CBR%20%2F%3ETo%20open%20a%20ticket%20with%20MS%2C%20just%20log%20into%20the%20M365%20admin%20center%20(admin.microsoft.com)%20and%20go%20to%20Support%20%26gt%3B%20New%20Service%20Request.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-475248%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-475248%22%20slang%3D%22en-US%22%3EOn%20Mac%2C%20the%20equivalent%20folder%20is%3CBR%20%2F%3E%3CBR%20%2F%3E%2FUsers%2F%5Busername%5D%2FLibrary%2FApplication%20Support%2FMicrosoft%2FTeams%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-542143%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-542143%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F258981%22%20target%3D%22_blank%22%3E%40sorendk%3C%2FA%3E%26nbsp%3B%20%26nbsp%3BNone%20reopened%20with%20a%20new%20number%26nbsp%3B%5BTicket%20%23%3A14147872%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-543331%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-543331%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20the%20same%20thing%20in%20our%20tenant%2C%20it%20happened%20to%20one%20of%20my%20messages%20as%20well.%26nbsp%3B%20Logging%20out%20and%20back%20in%20fixes%20it%2C%20but%20each%20person%20has%20to%20do%20that%20in%20order%20to%20see%20the%20message.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-636155%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-636155%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20checking%20in%20to%20see%20if%20there%20is%20any%20new%20updates%20on%20this%20issue%3F%26nbsp%3B%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-687339%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-687339%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F92167%22%20target%3D%22_blank%22%3E%40Joe%20McGowan%3C%2FA%3E%26nbsp%3BNope%20MS%20still%20chasing%20their%20tales....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20had%20me%20run%20POSH%20CMDS%20to%20verify%20its%20not%20retention.....I%20have%20message%20in%20one%20team%20that%20are%20gone%20in%20MAY%20but%20in%20other%20Team%20site%20they%20are%20missing%20in%20other%20months%20so%20clearly%20not%20retention.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-690361%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-690361%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3Bthanks%20for%20posting%20about%20this%20issue%20and%20the%20fix%20found%2C%20very%20helpful!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-693171%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-693171%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F242679%22%20target%3D%22_blank%22%3E%40melhity%20adm%3C%2FA%3E%26nbsp%3BNo%20official%20fix%20from%20MS%20yet%20that%20I%20know%20of.%26nbsp%3B%20The%20clearing%20of%20Cache%20is%20a%20temp%20fix%20as%20I%20have%20done%20this%20but%20the%20issue%20resurfaces.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700135%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700135%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3BWe%20are%20also%20still%20seeing%20this%20issue%2C%20and%20it's%20reported%20by%20our%20users.%26nbsp%3B%20Sometimes%20I%20wish%20microsoft%20would%20just%20read%20the%20message%20boards%20and%20see%20that%20it's%20not%20one%20person's%20retention%20policy%2C%20but%20an%20issue%20affecting%20multiple%20tenants!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700153%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700153%22%20slang%3D%22en-US%22%3EIm%20still%20waiting%20on%20MS%20to%20get%20back%20to%20me.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-700170%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-700170%22%20slang%3D%22en-US%22%3EThey%20are%20around%2C%20but%20as%20everyone%20else%2C%20they%20aren%E2%80%99t%20searching%20for%20problems!%20That%E2%80%99s%20why%20it%E2%80%99s%20important%20to%20report%20it%20to%20them%20via%20a%20ticket%20for%20example!%20That%20way%20they%20know%20somethings%20up%20when%20they%20receive%20several%20tickets%20about%20the%20same%20issues%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313819%22%20slang%3D%22en-US%22%3ETeams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313819%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20this%20on%20root%20conversations%20in%20some%20of%20our%20channels.%26nbsp%3B%20We%20thought%20it%20was%20someone%20in%20our%20group%20but%20we%20verbally%20confirmed%20no%20one%20deleted%20these%20Conversations.%26nbsp%3B%20The%20replies%20however%20are%20not%20deleted.%26nbsp%3B%20My%20CIO%20noticed%20that%20this%20is%20also%20happening%20on%20another%20Teams%20Channel%20he%26nbsp%3Bwas%20invited%20to%20to%20at%20another%20Firm.%26nbsp%3B%20So%20its%20not%20just%20us%20it%20seems.%26nbsp%3B%20Anyone%20have%20a%20clue%3F%26nbsp%3B%20I%20tried%20Audit%20logs%20but%20they%20on%20track%20Team%20and%20Channel%20deletions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-313819%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EActivity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EConversations%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-739338%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-739338%22%20slang%3D%22en-US%22%3E%3CP%3EI%20just%20wanted%20to%20post%20a%20follow%20up%2C%20this%20is%20still%20not%20resolved%20and%20I%20am%20still%20waiting%20for%20the%20backend%20team%20to%20figure%20out%20what%20the%20issue%20is.%26nbsp%3B%20Im%20basically%20stuck%20until%20they%20get%20back%20to%20me.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-750294%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-750294%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20keeping%20us%20in%20the%20loop%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E.%20We're%20experiencing%20the%20same%20issue%20as%20well%20and%20the%20fixes%20above%20only%20last%20about%205%20minutes.%20In%20our%20case%2C%20it%20seems%20to%20only%20be%20affecting%20conversations%20in%201%20channel%2C%20everything%20else%20is%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20raised%20a%20ticket%20with%20Microsoft%20as%20well%20and%20referenced%20this%20thread.%20I'll%20post%20back%20as%20well%20if%20I%20learn%20anything.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-750699%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-750699%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20appears%20to%20be%20happening%20to%20us%20is%20when%20an%20older%20post%20gets%20replied%20to%20(and%20brought%20back%20to%20the%20bottom%20of%20the%20thread)%2C%20after%20x%20amount%20of%20time%2C%20the%20root%20message%20eventually%20changes%20to%20the%20'This%20message%20has%20been%20deleted'%20message%20in%20the%20Teams%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESimilar%20for%20others%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752336%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752336%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20that%20is%20the%20behavior.%20Update%20for%20my%20environment...%20we%20aren't%20experiencing%20the%20problem%20using%20Version%26nbsp%3B%3CSPAN%3E1.2.00.17057%20(32-bit)%2C%20July%202%2C%202019.%20We%20started%20deploying%2Fstandardizing%20via%20the%20Office%20365%20installation%20and%20before%20we%20did%20that%20I%20was%20running%20the%2064-bit%20version...%20I%20might%20have%20a%20machine%20with%20the%2064-bit%20version%20still%20on%20it.%20I'll%20sign%20in%20there%20and%20check%20later%20today.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752469%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752469%22%20slang%3D%22en-US%22%3E%3CP%3EI%20believe%20I%20am%20running%201.0%2064Bit%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228093%22%20target%3D%22_blank%22%3E%40Timothy%20Balk%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752551%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752551%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3BNot%20experiencing%20the%20issue%20in%201.2.00.13765%20(64-bit).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752562%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752562%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228093%22%20target%3D%22_blank%22%3E%40Timothy%20Balk%3C%2FA%3E%26nbsp%3Bwhere%20are%20you%20getting%20this%20version.%26nbsp%3B%20The%20version%26nbsp%3B%20I%20get%20from%20O365%20is%20not%20that%20version.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752566%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752566%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fteams.microsoft.com%2Fdownloads%23allDevicesSection%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fteams.microsoft.com%2Fdownloads%23allDevicesSection%3C%2FA%3E%26nbsp%3B-%20MS%20keeps%20this%20updated%20with%20new%20client%20installers%20as%20they%20compile%20them.%20For%20the%2032-bit%20version%20we%20are%20using%20the%20O365%20Office%20Installer%20to%20manage%20the%20Teams%20client%20installation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752577%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752577%22%20slang%3D%22en-US%22%3EMicrosoft%20Teams%20Version%201.2.00.17057%20(64-bit)%20is%20latest%20build.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752672%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752672%22%20slang%3D%22en-US%22%3EI've%20tested%20both%20the%2032-bit%20and%2064-bit%20versions%20of%201.2.00.17057%20and%20I%20get%20the%20same%20issue.%20I%20also%20tried%20uninstalling%20the%20full%20Office%20suite%20including%20Teams%20and%20re-installing%20with%20the%20same%20results.%20Right%20after%20a%20re-install%20everything%20shows%20up%20fine%20but%20within%20about%20an%20hour%2C%20messages%20start%20flipping%20to%20the%20deleted%20message.%20It%20almost%20looks%20like%20the%20Teams%20client%20has%20some%20sort%20of%20process%20that%20prevents%20old%20messages%20from%20loading%2C%20maybe%20for%20performance%20reasons%3F%3CBR%20%2F%3E%3CBR%20%2F%3EGuess%20I'll%20wait%20and%20see%20what%20Microsoft%20comes%20back%20with.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-752727%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-752727%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F127725%22%20target%3D%22_blank%22%3E%40Jamy%20Mulder%3C%2FA%3E%26nbsp%3B%20Agreed%20I%20am%20on%20the%20latest%20it%20seems%20and%20the%20issue%20is%20present.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-753201%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-753201%22%20slang%3D%22en-US%22%3E%3CP%3EMaybe%20uninstall%20Teams%2C%20ensure%20that%20the%20app%20data%20file%20caches%20are%20cleaned%20from%20the%20user%20profile%20and%20re-install%3F%20This%20may%20be%20an%20additional%20step%20we%20did%20since%20we%20wanted%20to%20move%20from%20user%20based%20installation%20to%20the%20managed%20installation%20in%20Office%20365.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-770700%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-770700%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228093%22%20target%3D%22_blank%22%3E%40Timothy%20Balk%3C%2FA%3E%26nbsp%3B%20Been%20there%20done%20that.%26nbsp%3B%20Temp%20fix%20is%20to%20clear%20the%20cache%20which%20yes%20fixes%20my%20issue%20but%20not%20the%20root%20cause.%26nbsp%3B%20The%20issue%20returns%20within%20hours%2C%20so%20I%20cant%20keep%20doing%20this%20over%20n%20over.%26nbsp%3B%20I%20think%20MS%20should%20fix%20the%20root%20cause.%26nbsp%3B%20That%20being%20said%20I%20was%20told%20yesterday%20by%20MS%20that%20there%20is%20an%20internal%20bug%20report%20about%20this%20and%20that%20an%20update%20is%20coming%20in%20Aug%202019.%26nbsp%3B%20I%20dont%20buy%20it%20since%20this%20is%20teh%20same%20thing%20i%20was%20told%20in%20Jan%202019%20and%20an%20update%20was%20coming%20in%20May%20to%20fix%20this....BULL!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-771583%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-771583%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3BDo%20you%20have%20a%20TAM%20at%20Microsoft%20that%20you%20could%20reach%20out%20to%20so%20they%20can%20help%20out%20with%20this%3F%20They%20may%20be%20able%20to%20dig%20in%20and%20help%20clarify%20what's%20going%20on%20with%20the%20fix.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-773750%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-773750%22%20slang%3D%22en-US%22%3E%3CP%3EQuick%20Update%3A%20I'm%20still%20working%20with%20Microsoft%20on%20this.%20They%20released%20a%20new%20version%20(%3CSPAN%3E1.2.00.19260)%3C%2FSPAN%3E%20recently%20and%20thought%20that%20may%20have%20fixed%20it%2C%20but%20we're%20still%20experiencing%20the%20same%20issue.%20Will%20report%20back%20when%20I%20know%20more.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-774242%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-774242%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F127725%22%20target%3D%22_blank%22%3E%40Jamy%20Mulder%3C%2FA%3E%26nbsp%3BI%20was%20told%20an%20update%20is%20coming%20in%20Aug%202019.%26nbsp%3B%20I%20am%20still%20waiting%20to%20hear%20back%20from%20them.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-794433%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-794433%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20you%20for%20sharing%20this%20information%20to%20us.%20May%20we%20know%20if%20there's%20a%20reference%20ticket%20or%20page%20article%20for%20this%3F%20We%20have%20been%20experiencing%20the%20same%20issues%20but%20we%20need%20to%20provide%20the%20reference%20to%20our%20users.%20Thank%20you%20in%20advance.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-795844%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-795844%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F388987%22%20target%3D%22_blank%22%3E%40Ahriz_MusicTribe%3C%2FA%3E%26nbsp%3BThere%20is%20an%20internal%20bug%20report%20MS%20has%20issued%20but%20they%20are%20reluctant%20to%20provide%20that%20information%20to%20me.%26nbsp%3B%20%26nbsp%3B%20I%20have%20opened%20a%20ticket%20with%20MS%20and%20its%20currently%20being%20held%20by%26nbsp%3B%3C%2FP%3E%3CP%3ESupport%20Escalation%20Engineer.%26nbsp%3B%20Unfortunately%20that%20all%20the%20info%20I%20have%2C%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-796141%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-796141%22%20slang%3D%22en-US%22%3EThat's%20the%20same%20information%20I'm%20getting.%20The%20product%20group%20said%20they%20have%20a%20fix%20that%20should%20resolve%20the%20issue%2C%20however%20they%20don't%20have%20an%20ETA%20yet%20on%20deploying%20the%20fix.%20Hopefully%20soon!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-797764%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-797764%22%20slang%3D%22en-US%22%3E%3CP%3EWas%20just%20old%20update%20bumped%20to%20Sept.%202019.....%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22I%20have%20an%20update%20regarding%20the%20ETA%20of%20the%20fix%20for%20the%20issue.%20As%20this%20will%20be%20rollout%20for%20all%20customers%2C%20it%20is%20taking%20more%20time%20than%20expected.%20Engineering%20Team%20is%20targeting%20Q3%20end%2C%20which%20is%20September%E2%80%992019.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-816625%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-816625%22%20slang%3D%22en-US%22%3EMy%20company%20is%20having%20this%20problem.%20We%20have%20to%20log%20in%20and%20out%20to%20see%20the%20message%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844262%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844262%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EStill%20seeing%20this%20%3C%2FSPAN%3Eissue%20in%20September!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844282%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844282%22%20slang%3D%22en-US%22%3EUpdate%20I%20got%20on%20September%206th%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%22We%20are%20following%20up%20with%20the%20backend%20to%20get%20an%20ETA%20for%20the%20fix%2C%20hence%20as%20soon%20as%20we%20have%20it%20will%20share%20the%20same%20with%20you.%22%3CBR%20%2F%3E%3CBR%20%2F%3EI'll%20post%20back%20when%20I%20hear%20more.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-927635%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-927635%22%20slang%3D%22en-US%22%3EUpdate%20never%20came%2C%20surprise%20surprise.%20Now%20pushed%20to%20Oct%202019.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-983073%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-983073%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F87754%22%20target%3D%22_blank%22%3E%40Christian%20Taveras%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20experiencing%20the%20same%20problem%20here%2C%20any%20update%20since%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-989296%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-989296%22%20slang%3D%22en-US%22%3EUpdate%20I%20got%20today%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%22The%20PG%20has%20a%20fix%20for%20this%20issue%20which%20from%20what%20I%20can%20gather%20is%20in%20the%20deployment%20phase%20now.%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20should%20get%20more%20info%20early%20next%20week%2C%20I'll%20post%20back%20when%20I%20do.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-989706%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-989706%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F127725%22%20target%3D%22_blank%22%3E%40Jamy%20Mulder%3C%2FA%3E%26nbsp%3BThere%20was%20an%20issue%20they%20ran%20into%20and%20stopped%20deployment.%26nbsp%3B%20Only%20a%20few%20tenants%20got%20the%20update.%26nbsp%3B%20At%20least%20thats%20what%20i%20was%20told%20by%20level%202%20support%20who%20spoke%20to%20the%20DEV%20team.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1038865%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1038865%22%20slang%3D%22en-US%22%3E%22The%20target%20date%20for%20full%20WW%20deployment%20of%20the%20fix%20is%20the%20second%20week%20of%20December.%22%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20was%20deployed%20to%20our%20tenant%20ahead%20of%20time%20and%20has%20resolved%20the%20issue%20for%20us.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1042365%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1042365%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F127725%22%20target%3D%22_blank%22%3E%40Jamy%20Mulder%3C%2FA%3E%26nbsp%3B%2C%20what%20version%20of%20the%20Teams%20client%20are%20you%20now%20running%3F%26nbsp%3B%20Just%20curious%20if%20that%20will%20indicate%20the%20version%20that%20has%20the%20fix.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks!%3C%2FP%3E%3CP%3EMary%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1042396%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20%3A%20This%20message%20has%20been%20deleted.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1042396%22%20slang%3D%22en-US%22%3E1.2.00.31357%20(64-bit)%3C%2FLINGO-BODY%3E
Frequent Contributor

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.

63 Replies
How many messages are we talkin? Wondering if something GDPR / Compliance related could be stripping them out, but I don't think there is anything in just yet to single out individuals.

Its very random and its posts that do not have any kind of sensitive data.

 

 

 

This conversation is in reference to an OU in AD, nothing sensitive there...

 

Its not retention as that is set for a year and there are posts in Oct 2018, 1 of the 5 post in that month got DEL.
Maybe creating a ticket with MS is a good idea..

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.

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.

... Ticket opened.

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.

 

%appdata%\Microsoft\teams\application cache\cache

%appdata%\Microsoft\teams\blob_storage

%appdata%\Microsoft\teams\Cache

%appdata%\Microsoft\teams\databases

%appdata%\Microsoft\teams\GPUcache

%appdata%\Microsoft\teams\IndexedDB

%appdata%\Microsoft\teams\Local Storage

%appdata%\Microsoft\teams\tmp

It's easier to just delete that whole teams folder :P.

Did you ever try to do a log off and log on? That seems to sometimes clear out cache issues usually because it fixes many issues that quit / starting / rebooting will not fix with Teams.

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.  

Agree, but it's a lot easier to click your photo and sign out than mess with cache issues directly :p.
Maybe scripting a deletion of the cache folders and put it as a scheduled task or autorun? :face_with_tears_of_joy:
Seeing the same issue, and log out\in resolves it. Hoping a better fix comes soon

Logging out/logging in to Teams resolves the problem for us too, but usually only for about a day or so before the problem crops up again.

@Timothy Balk , did MS ever get back to you on the ticket you opened?

I finally got some sort or answer on this from Microsoft via the ticket i opened.,....

 Ricky (Microsoft)
Monday, March 4, 2019 10:02 PM GMT
Hello Admin,

Greetings

Thank you for your reply.

I would be glad to share the root cause of the issue however this is the findings for now and the case is still getting investigated by the internal team.

Would be fixed by the end of march.

After investigation, we found out the alerted message is marked as deleted in local Teams client, but after sync with Teams server, the message is recovered, and deleted flag disappears. Seems like there is a sync issue between Teams client Local Cache and Teams server.

If you have any issue please feel free to contact us, I will be more than happy to assist you.

Thank you for contacting Microsoft Support.


Best Regards,
Ricky Dhiman
Microsoft O365 Support Team
Working Hours :- Monday to Friday 08:00 AM to 05:30 PM EST


@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. 

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 

@owtucker Ticket #12790064

@Christian Taveras 

 

We're seeing this issue as well, on couple of Teams.

Any news on the ticket that was reported to Microsoft?

@Christian Taveras  , Since last week, my customer tenant also affected.

 

We use Microsoft Teams as a communication platform for all staff at my school. We are noticing that conversations threads are getting deleted. I have asked around the teachers who are the 'Owners' and no one is deleting them. Has anyone experienced this before? Thanks so much. I am only new to Teams. please help this is getting frustrating. I dont know where to go.. All conversation threads have been deleted in all our channels back to when we started TEAMS in March HELP Please. How do I log a support ticket?

@JBeven, if you're having the same problem as others on this thread, signing out of Teams and signing back in seems to restore the deleted threads, at least temporarily. Do this by clicking on the user's photo in the upper right-hand corner of the app.
To open a ticket with MS, just log into the M365 admin center (admin.microsoft.com) and go to Support > New Service Request.
On Mac, the equivalent folder is

/Users/[username]/Library/Application Support/Microsoft/Teams

@Deleted   None reopened with a new number [Ticket #:14147872]

We are seeing the same thing in our tenant, it happened to one of my messages as well.  Logging out and back in fixes it, but each person has to do that in order to see the message.  

Just checking in to see if there is any new updates on this issue?  Thanks.

@Joe McGowan Nope MS still chasing their tales....

 

They had me run POSH CMDS to verify its not retention.....I have message in one team that are gone in MAY but in other Team site they are missing in other months so clearly not retention.

@Christian Taveras thanks for posting about this issue and the fix found, very helpful! 

@melhity adm No official fix from MS yet that I know of.  The clearing of Cache is a temp fix as I have done this but the issue resurfaces.

@Christian Taveras We are also still seeing this issue, and it's reported by our users.  Sometimes I wish microsoft would just read the message boards and see that it's not one person's retention policy, but an issue affecting multiple tenants!

Im still waiting on MS to get back to me.
They are around, but as everyone else, they aren’t searching for problems! That’s why it’s important to report it to them via a ticket for example! That way they know somethings up when they receive several tickets about the same issues

I just wanted to post a follow up, this is still not resolved and I am still waiting for the backend team to figure out what the issue is.  Im basically stuck until they get back to me. 

Thanks for keeping us in the loop @Christian Taveras. We're experiencing the same issue as well and the fixes above only last about 5 minutes. In our case, it seems to only be affecting conversations in 1 channel, everything else is fine.

 

I've raised a ticket with Microsoft as well and referenced this thread. I'll post back as well if I learn anything.

What appears to be happening to us is when an older post gets replied to (and brought back to the bottom of the thread), after x amount of time, the root message eventually changes to the 'This message has been deleted' message in the Teams client.

 

Similar for others?

Yes, that is the behavior. Update for my environment... we aren't experiencing the problem using Version 1.2.00.17057 (32-bit), July 2, 2019. We started deploying/standardizing via the Office 365 installation and before we did that I was running the 64-bit version... I might have a machine with the 64-bit version still on it. I'll sign in there and check later today.

I believe I am running 1.0 64Bit, @Timothy Balk 

@Christian Taveras Not experiencing the issue in 1.2.00.13765 (64-bit).

@Timothy Balk where are you getting this version.  The version  I get from O365 is not that version.

@Christian Taveras https://teams.microsoft.com/downloads#allDevicesSection - MS keeps this updated with new client installers as they compile them. For the 32-bit version we are using the O365 Office Installer to manage the Teams client installation.

Microsoft Teams Version 1.2.00.17057 (64-bit) is latest build.
I've tested both the 32-bit and 64-bit versions of 1.2.00.17057 and I get the same issue. I also tried uninstalling the full Office suite including Teams and re-installing with the same results. Right after a re-install everything shows up fine but within about an hour, messages start flipping to the deleted message. It almost looks like the Teams client has some sort of process that prevents old messages from loading, maybe for performance reasons?

Guess I'll wait and see what Microsoft comes back with.

@Jamy Mulder  Agreed I am on the latest it seems and the issue is present.

Maybe uninstall Teams, ensure that the app data file caches are cleaned from the user profile and re-install? This may be an additional step we did since we wanted to move from user based installation to the managed installation in Office 365.

@Timothy Balk  Been there done that.  Temp fix is to clear the cache which yes fixes my issue but not the root cause.  The issue returns within hours, so I cant keep doing this over n over.  I think MS should fix the root cause.  That being said I was told yesterday by MS that there is an internal bug report about this and that an update is coming in Aug 2019.  I dont buy it since this is teh same thing i was told in Jan 2019 and an update was coming in May to fix this....BULL!

@Christian Taveras Do you have a TAM at Microsoft that you could reach out to so they can help out with this? They may be able to dig in and help clarify what's going on with the fix. 

Quick Update: I'm still working with Microsoft on this. They released a new version (1.2.00.19260) recently and thought that may have fixed it, but we're still experiencing the same issue. Will report back when I know more.

@Jamy Mulder I was told an update is coming in Aug 2019.  I am still waiting to hear back from them.

Related Conversations
Delete Messages Teams
cvillanueva in Microsoft Teams on
1 Replies
Teams error code - 6
damnit95 in Office 365 on
4 Replies
Sharing a Teams Calendar
Michael Krueger in Microsoft Teams on
16 Replies
Skype Room System stuck on signing in (Solved)
ckoppen in Microsoft Teams on
27 Replies
Teams Updater Vulnerability
Andrew Matthews in Microsoft Teams on
15 Replies