Forum Discussion
No new messages in desktop client after switching organisation
Hello,
we have the following problem: Using Windows Desktop Client and we have user which are switchting with this client between own and partner organisation.
When they swtich back to own organisation in client they get no new messages.
They have to close the Teams client and restart the client.
Web browser and mobile client have no problem.
We got information from other company, that they have same problem.
Regards
- Hi everyone - This issue should now be resolved. Please report back if you're still seeing this. We released a new build (1.0.0.2021101136) last week which has been rolled out 100% to R4 to fix this. Please request users to sign out and sign back in to ensure that they receive the latest build.
Same issue here running 1.4.00.22265 on Mac OSX. My Teams was updated today to this version, however I had the same issue on the previous version.
- Same problem here on 1.4.00.26376
Update:
I have raised a ticket with MS, they came back with this:
"Yes, many tenants are experiencing the same issue. it is a known bug and the Teams backend engineering team is currently developing a fix to resolve the issue. they advised that the issue will be rectified in two weeks time. in the meantime users can use the web client while waiting for the issue to be resolved.
Thank you for your time and cooperation. We will be waiting for your feedback."
They have accepted fault - fix due in a few weeks.UPDATE 12/10:
They tried to close off the case saying they have given a 'resolution' and cant leave the case idle. I objected, forcing them to keep the case open and now our tenant is on a priority list for the patch release.
I would advise everyone else to do the same. Try and make sure they dont close off any cases in regards to this because 'Use this workaround and wait for the update' isn't a good enough answer.
Thanks
SeanCame to this forum solely to inquire about this issue that we've been having for weeks now. Thanks for the info and the leg work, Sean.
I'm pretty outraged, because this is a dead in the water bug for several of our clients.. Microsoft seems to have such a cavalier attitude towards these disruptions - "Just do x instead of y while we spend a few weeks taking our heads out of our collective a*ses", all the while taking forever to even acknowledge the issue, and not communicating anything to anyone. Do they understand how businesses operate? If they do, then they should know that you can't just expect an entire organization to change the way they do things on a dime. It would take that long just to arrange to re-train users. Not a viable workaround.- I fully agree -- I don't see how this "we'll fix this in a couple of weeks" attitude is acceptable.
The workaround is a joke. Teams messaging not working is equivalent to phones or e-mail not being operational in a modern organization.
- SeanWatkins I also got told it will be fixed late October.
- How do I log a ticket with Microsoft? Do I need to get someone from my company it support to raise the ticket?
- Hi Gill,
Yes you will need to contact you IT support team. They should be able to raise a case for this in their O365 admin portal.
Thanks
Sean
- Sam Cosby
Microsoft
Hi everyone - This issue should now be resolved. Please report back if you're still seeing this. We released a new build (1.0.0.2021101136) last week which has been rolled out 100% to R4 to fix this. Please request users to sign out and sign back in to ensure that they receive the latest build.Read receipts still seem to be broken for all our users. Also, what does that build # correspond to? We see "Version #1.4.00...." in the About menu.
- Sam CosbyCan you clarify further on your issue? Did this just start happening? Is it for just read receipts or all messages?
- Hello Sam, in our organization the error still occurs sporadically with some users.
When the organization is changed, the teams sometimes hangs completely and can only be fixed by restarting the device.
The clients are all running on version 1.5.00.17656 .Jonas_621 Have you found any updates to this issue? We are still experiencing it. We are running version 1.5.00.33362
Marc Mönnikes We are experiencing the exact problem and are eager to get it solved.
Please reply with an answer or that you are working on it. Pernille-Eskebo- We are having the exact same issues. Does not affect mobile app only Desktop app. We are having to either logout / exit Teams altogether and log back in again or simply stop switching. Is this related to an update 1.4.00.22472?
- same issue for mac os 10.14.6 and 1.4.00.22368 teams version (web and mobile work good)
issues here too - especially when switching organizations -> browse or edit files -> switching back Org - no new chats, whole chat window loading spinner of death etc. - even in teams web - can receive messages but messages sent do not arrive!
Microsoft: why haven't you left us any feedback on this issue yet? I'd consider this a major issue.
- This issue is killing us - Sept 23rd and still experience it, reported it, and no health advisory or issue in the M365 admin center anymore. What the actual f....Maybe everybody at MS too busy oooing and aaahing at the Surface devices announced yesterday? 😉
Marc Mönnikes Same problem here.... this is killing internal and external communication... should we go back to Slack? Anyone who found a workaround? or even better fix?
- No fix, but more importantly, no word/announcement/status from MS. This affects those of us who work with multiple organizations, possibly in a support role, which means for every one of us that experiences this, 100's if not 1000's of our users are affected because their messages aren't getting through to us. So while it may be a minority or seemingly "small number"of direct users that are encounting this issue, its affecting many many more indirectly.
- The same problem here - we switched temp. to web-client (teams.microsoft.com).
