Forum Discussion
Status does not update (New Teams)
Hi,
We've been testing the new Teams before we roll it out more widely. We have noticed that your status does not update consistently with the new Teams, as in, here is one scenario as an example
- I'm showing as available and somebody calls me (working well at this point)
- I pick up the call and when I do I show as busy (still all going well)
- I present during the call and the status changes to do not disturb (so far so good still)
- I end the call, but my status stays as do not disturb indefinitely until I click on reset status. (this is the behaviour that didn't used to happen in classic Teams)
All throughout the above I did not manually change my status; it was just updating automatically as my activity changed, but did not update in the end when my call ended.
Is anyone else experiencing this and is there a way to fix this?
Thanks,
Andrea
- We're seeing this now at our organization on anyone using the new Teams client, the presence indicators no longer change at all based on activity. Sign out/back in, as well as 'reset status' resets it to the current condition, but go into a meeting or take a call and it remains whatever it was when you reset. The indicators don't change at all, across all our machines using the new Teams. Editing registries or manually deleting/clearing the cache is not an option. This started around the beginning of the month and has only gotten worse, and spreading (or people are just starting to notice). We rely on this and it's a mess.
- Another Update: In my frustration, I reverted back to Classic Teams yesterday and completely uninstalled "NEW" teams. I had ZERO issues yesterday. I made a Teams to Teams call this morning and noticed that my co-workers statuses were off again. My smart phone (Android) was showing correctly. So now classic Teams is affected too? VERY strange stuff. Logged out and back in and the statuses were fine. I plan on doing more extensive troubleshooting today and will post anything I find in my logs. Good luck everyone and happy Friday.
Darksabre oh no! Yes weird. Hmmm…did they maybe manually change their status? You know how in classic if you manually change your status, it will stay that way unless you reset…? 🙂
Interesting. I've started to see the issue since we switched our telephony solution from VOIP to Operator Connect AND switched to the New Teams. Thank goodness the switch from Classic Teams has not been rolled out to the enterprise yet. This being said we have had a report today from one of our users, I've yet to find out if she is using Classic or New Teams.
An annoying bug that needs to be addressed!
- Was your co-worker using Teams-Classic or the New-Teams?
I have also noticed that the status in the app (ios for me) is often correct, also in the web app.
In problematic cases, it may be indicated as "unknown".- great question. she's on Classic Teams. Weird, right?
- We have been experiencing the same issue with new Teams for a few weeks. From testing, we think that part of the issue is traffic that should be proxied may not be. Can't pinpoint it, but we are seeing traffic from Teams hit the firewall, which could indicate it is not being proxied, and therefore potentially causing at least some of the issues.
https://techcommunity.microsoft.com/t5/microsoft-teams/new-teams-honoring-proxy/m-p/3970918/highlight/true#M129068- I had the same suspicion, but the problem has only been occurring in our company since the update at the end of October and also affects people who work at other locations and at home. However, I don't think a normal home router will block data traffic from Teams.
- I agree, however to date I've been unable to reproduce the presence issue on a non-company PC. Curious if you are seeing the same?
- We have also been having a lot of inconsistencies with presence. I logged in this morning and had status of unkown for roughly 30% of the people I chat with regularly. My own status is uknown and I cannot change it. Uninstall and reinstall is not a good work around. I had to switch back "old" Teams.
Interesting that one of the first comments in this thread recommends not putting computer to sleep. My computer goes to sleep nightly (I don't log off or reboot). I was on a call with MS yesterday and they had me restart New Teams client and it worked for the rest of the day. This morning after the computer returned from sleep a lot of the status' were wrong again. Restarting the New Teams client fixed it again. This may be an issue with having the computer go to sleep in my instance.
Is sleep and New Teams a known issue?
Our computers do not go into sleep or standby mode. Our devices are always switched off.
The problem occurs both for people with several devices and for people with just one device.
I think it is actually due to the software. And even if it isn't, it should be able to handle it.
- I have spoken with Microsoft quite a lot over the past 24 hours to look into this issue and they don't seem to even acknowledge this as a bug. But I think this was more the support agent issue.
At first he tried to tell me because I was on the New Teams I was running a Beta version and I had to show him the documentation to show him it was now under general availability. Along with lots of other time wasting exercises he ended the call by saying 'Use the classic Teams and try the new teams again in a week to see if the bug has been fixed'
Pretty poor but I am trying to get them to acknowledge the bug at least so hopefully a fix comes soon as it was very frustrating for my users all of a sudden they stopped working. I moved it into default for some users to test it before moving to full organisation and had to revert them all back after 24 hours.- VERY typical of Microsoft Support. My ticket has been escalated, but no response yet since there is a "work around." @andrea2020 have you gotten any updates from your ticket yet?
Darksabre No resolution on the ticket we logged either, just a lot of questions to which we've reiterated that it's affecting everyone and that it started and is affecting only the New Teams. Luckily for us we started deploying with only a pilot group and so is manageable. We're holding off on deploying it organisation-wide.
Same here.
Microsoft Teams 23285.3604.2469.4152. (49/23101227708) 9.11.2023.
They know, but when will it be fixed? Till then I'm using MSTeams1.6
Known issues in the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learnbut
What's new in the new Teams app - Microsoft Support
???
We have also the Version: Microsoft Teams 23285.3604.2469.4152
I don't find the Problem under "Known issues in the new Microsoft Teams desktop client - Microsoft Teams | Microsoft Learn"
- We've been dealing with this in org for a couple of weeks now with many staff members complaining. Definitely feels like the latest update to the New Teams client is the cause. We've had a support ticket open with MS for two weeks but no indication of a fix being issued yet. It would be good if they would at least acknowledge it in the Service Health dashboard as an active issue, but nothing yet.
- Here is a small contribution from Germany
We are also struggling with status problems in the new teams. People who leave a meeting or a call are often still shown as "in conversation" afterwards. Others are still shown as "Active" for hours after shutting down their computer.
We have been experiencing these problems since the end of October. We have opened a ticket with support, let's see what happens.
But I also think that a final solution will have to be found by Microsoft. We didn't have any status problems in the new Teams before the end of October. - To add to add a bit more information, and to confirm it’s definitely the New Teams, I have Teams on my mobile device (iphone) and have notifications turned on. After taking a call on my laptop, I didn’t notice my status stayed as “do not disturb” (I already know this could happen right, but I still forget to update status after each call/meeting! and you really shouldn’t need to anyway, hence this post, but back to story….) I only realised my status was still “do not disturb” because a Teams call rang on my phone but not in my laptop.
So yeah, still trying not successful at finding an org-wide solution 😞 starting to give in to the idea that maybe there is nothing we as an organisation can do, and only Microsoft can come to the rescue - We've been seeing similar behaviour, but one of our macOS users also reported an interesting behaviour that may be connected: when he moves from one device to another he sees the banner across the top of the Teams client informing him that he's on a call on another device, and would he like to transfer it to this machine. He was not on a call, at least not recently. His last call was finished some time ago, but the banner persists.
Teams presence status, macOS at least (my main platform), doesn't cope well with being logged in on more than one device at once. I tend to leave my desktop machine logged in 24/7, with the screen locked when I'm away from my desk or not at work. The screen locked/away presence set by this machine overrides whatever I'm doing on any other device.lboro_garypYou bring up a very interesting point. I have a two MacBook Pro's, both running Teams, one is locked all day and serves as my backup. I'll shut down Teams on the backup system and see if that makes a difference. That backup machine also happens to be running the "old" Teams Classic, whereas, my primary system is on the new Teams.
- @lboro_garypY I'll be darned, that was my problem. I was running Teams on two desktop devices (Macbooks) and my status would always show green. I quite Teams on the second device and now my status is working as it should. I'm still logged into Teams on my iPhone and that's also working as expected. That all said, we have other users on Windows that have similar status issues and are only logged into one device.
