Forum Discussion
MS Teams delay DM's
VSILVR10 Hey, a colleague of mine had a similar issue today actually. He first did a manual sign out / sign in using the Teams desktop client and it got a bit better. But when he deleted the entire Teams desktop cache the problem was solved. So.
1. Sign out and back in using the Teams desktop app.
If no success.
2. Delete the Teams app cache (go to start button and type %appdata%\microsoft\teams and press enter. Delete the content in the Teams folder).
If on a Mac ~/Library/Application Support/Microsoft/Teams
VSILVR10 Hey, a colleague of mine had a similar issue today actually. He first did a manual sign out / sign in using the Teams desktop client and it got a bit better. But when he deleted the entire Teams desktop cache the problem was solved. So.
1. Sign out and back in using the Teams desktop app.
If no success.
2. Delete the Teams app cache (go to start button and type %appdata%\microsoft\teams and press enter. Delete the content in the Teams folder).
If on a Mac ~/Library/Application Support/Microsoft/Teams
ChristianBergstrom I suggest, don't delete the teams folder. I recommend users always rename the folder instead. Why?
- If you delete, then you don't have a backup unless you first make a copy, which might or might not work as you expect if some files are locked.
- A delete may not purge some files such as files that are locked. If you are deleting, you really want to delete all, to start clean.
- If any files are locked, a rename will fail, offering the opportunity to determine what has your files locked (which is likely a Teams process that should be terminated) helping to ensure you are re-starting Teams clean.
- If you rename, when you restart Teams, a new, empty Teams folder will first be created by Teams, applying Teams business rules, ensuring a clean start. (If you create the folder manually, you could be bypassing some Teams logic...)
- If this approach doesn't work for any reason, you can restore the renamed folder to return to the previous state.
All said, this approach, to re-start Teams with a clean folder works for me. I've had to repeat this exercise as my issues eventually resurface in the future for whatever reason.