Forum Discussion
New bug? Presence issue when switching to different orgs
The latest update to Teams desktop client 1.3.00.30866 (64-bit) seems to have broken presence indication for us. We noticed that it's happening when switching among orgs that you're a guest in.
What I've noticed is that if you launch Teams, you default to the last Org you were set to - and for that, presence works correctly, but if you switch to a different org, presence is no longer shown. It only seems to be available for the initial org you land in when launching the app.
I've submitted a bug report, but has anyone else noticed this? I've done the usual troubleshooting, including clearing the local Teams cache.
1. Launch Teams - land into last open org - Presence looks ok:
2. Switch to a different Org (several orgs available to switch to, doesn't matter which one):
3. Presence info not available
- No worries Bob, that's now raised internally with the product team referencing this thread and the associated uservoice. Let's hope this is remediated in the next few days or so
Best, Chris
4 Replies
Hey Bob,
I had the problem recently and clearing the cache from this particular doc resolved it
https://commsverse.blog/2018/09/28/clear-the-microsoft-teams-client-cache/Some clear cache docs are different but this seems the most thorough one and works for me 99% of the time. If you have done all this then would advise opening a ticket. I have raised the bug here and informed the product team, so you may want to update your ticket to avoid them asking you to do it
Hope it gets resolved! Hope it will soon
Best, ChrisChrisHoardMVP Hey Chris thanks, yes I had actually already done the usual cache clearing exercises, uninstalled/reinstalled, tried on a few machines/different accounts. Also had submitted a bug report to Teams UserVoice prior to posting here. We'll see.
(Also, FWIW, if I back-rev to the previous client version, it works. Once I update to the latest, it doesn't.)
- No worries Bob, that's now raised internally with the product team referencing this thread and the associated uservoice. Let's hope this is remediated in the next few days or so
Best, Chris
