Forum Discussion
Status does not update (New Teams)
Hello everyone,
As promised, here is some feedback from Microsoft Support. Unfortunately, I was traveling externally and couldn't speak to the agent, so he sent me an email.
I will post the text here. I will provide the information by e-mail tomorrow. The only thing is that reproducing the error in a video will probably not work. The error does not always occur.
Maybe someone can do the "Synchronization, Notification, Availability, and Automatic Replies" test with the Microsoft Analyser again. With two different accounts in different tenants, I always get an error at the last step in the calendar. Perhaps a possible cause.
So here the Message from Microsoft:
- Do you have the same issue with Web version and Classical Teams App ?
Thank you in advance.
You shouldn't need a video to repro the presence issue. Just take a screenshot of your contacts in the web client right next to the full client and that should convey the issue.
Here's a screenshot of the update problem if you need it:
We also have a case open and MS has this same info.
- MarkusM1610Nov 14, 2023Brass ContributorYes, also with the 4152. We already had the problems in October with the 769 and had hoped that the update would improve the situation. But unfortunately that wasn't the case. The problem persists.
It updated to the 4152 automatically at the beginning of November.
I check every day to see if there is a newer version to test.
Long story short. The problem existed or still exists under 769 and also under 4152. - DennisEngNov 14, 2023Copper ContributorI'm on .4152 now and statuses seem to be working as expected. Will update later on in the day if that's no longer the case.
- DaveTheTeamsGuyNov 14, 2023Iron Contributor
Are you seeing the error with .4152? Did the client automatically update past .769, or did you have to manually update to .4152?
- MarkusM1610Nov 13, 2023Brass Contributor
The idea with the screenshot is great. Thanks for the suggestion.
And thanks for the photo of the version. We got a newer version than yours at the beginning of November. (23285.3604.2469.4152)
But we already had the same problem with the version you used