Cannot unsave a message from the saved list
I tried to unsave a message in the saved list, but the item won't disappear from the list. It is still on the list whenever I come back to the saved list.
"saved messages" would be a helpful tool to remember messages (e.g. you may have to answer to such a message, but you can not do it right now as you need to check something first).
But as "unsave" does not work, it gets somehow useless, as "done messages" can not be removed from the "saved messages" list.
Petr Svihlik commented
I'm running into this regularly. The only thing that helps is logging of an in again.
Debbi L. commented
I'd been having the same issue where a saved chat would not unsave. I resolved it by QUITting Windows client Teams from the hidden icons area, and then opening web Teams and closing it. My Saved list was finally clear. I agree this basic function should be fixed!
Jason Miller commented
Same issue here... And while we are at it can we make a saved items button on the side bar? That would be so much easier to get to as I use it all the time!
I have found that upon removing the saved item from the list, that I had to sign-out completely from Teams and close the program. Then when I reopen Teams and sign back in, my saved list is correct and the item is now removed.
Tobias Graf commented
Same issue here. You absolutely need to fix this soon. Saved list feature is not usable like this ...
R Bent commented
Agreed. In addition to the lagging integration of Posts with Planner (or whatever it is to be called now) not being able to reliably use the 'saved list' to track items I need to follow-up on is a major limitation.
Frederique H commented
Same issue! Please fix it, I was really counting on the Save this message option whenever I want to check something later and find it easily without worrying that it is buried under newer posts. However with the fact that it is impossible to unsave, the list of saved messages keeps growing and is impossible to sort through!
This is a basic issue, so please fix it.
Dennis Reusch commented
With MS Teams closed on my Mac, deleting the "IndexedDB" directory resolved the issue for me.
rm -r ~/Library/Application\ Support/Microsoft/Teams/IndexedDB/
When MS Teams is opened next, the directory is pulled from the cloud and all is well.
Still no solution? Or I just do something wrong?
I am having the same issue. Is Microsoft going to address this? I see that there were people having this issue in March. Are you any closer to finding a solution? Thanks!
I found an answer, you need to sign out rather than just close the window. I guess that clears the cache. When I signed back in, it no longer showed on my saved list.
Emre TOPTANCI commented
Same issue here.
Tried both unsaving from the saved messages list and the message's context menu, same result.
The issue happens on Desktop Client for me. Closing and relaunching the desktop client did not help but if I open the web client I see that the message is successfully unsaved and no longer in the list. For some reason, desktop client seems to refuse forgetting the message.
Stephen Nilsen commented
Same issue for me. Please fix!
same here in my organisation.
tried several ways (iPad sync to desktop and otherway).
there is no version (webapp, desktop app or mobil app) in which one can trust to save his messages.
why is this problem so much "under radar"?
Saved messages do not work well in Teams desktop app for PC :
. Sometimes saved messages do not appear immediatly in saved list (it works minutes or hours later)
. Others cannot be unsaved (from saved list with a clic on the little purple incon)
. Sometimes it seems that one saved message seems to be taken for another one
Overall, because of these bugs, it's hard to trust this "saved messages" functionnality while it should be an essential one: to monitor a "todo list" for messages we have read but which we will have to come back to later to deal with
Mark Portman commented
I have the same issue and find it very annoying as I use Saved messages to follow up on outstanding chats
Experiencing same issue. Is very annoying as it is a basic functionality, especially in order to manage messages in high volume. Hope a solution to this is found soon.