desktop app not reconnecting
Desktop app does not do a very good at reconnecting if it drops connection to wireless or network and then reconnects. It will try a couple of times, but then fails.
Please fix this issue. Chatting via teams loses it's effectiveness if you are not connected to the program! Moving around in the office is the way my company works, and employees are connected to network and wireless intermittently throughout the day - so it definitely is a waste of time to ensure you are connected to Teams.
van der Kolk commented
This issue is driving me nuts. I'm having to put the move to Teams on hold because we have too many missed messages.
This is ridiculous behavior for a virtual presence app. I can never trust it to be on as I move a lot around the office and need to manually hit the "reconnect" button several times a day. How can this not be a top priority?!?
People get furious at me because they think I ignore their messages. Please bring back Lync, that app WORKED A CHARM.
I can only wonder what it would be if my phone was also through Teams. I would miss so much calls. Glad I still have a hard phone on my desk.
- on an up to date Windows 10
This is still happening.
About the desktop app on Mac OS, sometimes when the network connection fails/reset/whatever, Teams won't reconnect properly. I've seen in cases that in the Chat, outbound messages will go out properly, but inbound messages won't be received or shown in the desktop app. I notice that because I also have teams in my phone. There, I see what I've sent and incoming messages, which won't show in the desktop app until I reset the app. Also, same issue as with Skype with incoming calls on Mac and PC. Sometimes, the app won't receive incoming calls, and only the phone will receive those and ring. Now, clicking on the update now to relaunch the app is annoying because I always have that window split with outlook, and that breaks my window setup.
Paul Won commented
This is still annoying me. I am on Mac.
Sonny Ramsay commented
A "Try to reconnect" button would allow me to easily retry the connection without having to close the app and relaunch it.
I think the solution to this is just lighting the application on fire and then using something else.
Arno Tolmeijer commented
I had a strange experience the last couple of days with Teams connectivity. At the office, the connection was great. At home, it was poor. I had to reinstall Teams to have an initial connection, consequtive connections failed - both wired and wireless.
Today I noticed Network Detetion was disabled. When I enabed it, Teams connected fine again, both wired an unwired.
It doesn't reconnect when VPN connects - real pain
Relates to https://microsoftteams.uservoice.com/forums/555103-public/suggestions/20612899-desktop-app-not-reconnecting and https://microsoftteams.uservoice.com/forums/555103-public/suggestions/19404844-teams-app-loosing-connection.
Incredibly irritating, please fix. On the first link I've made it clear what the expected behaviour is, both in terms of reconnection, and of handling messages posted whilst disconnected.
Teams handling of disconnect/reconnect is shockingly poor and constantly causes me issues as I often work in different locations/change networks. It's a pain in the neck: the thing needs to get out of my way and let me get on with my work.
Same problem. Teams is appalling at handling network changes, sleep/wake/reconnect, termporarily loss of connectivity. It's *incredibly* frustrating. Most of the time I'm forced to restart the app, which is also annoying because teams is *incredibly* slow to start up.
Seriously, here is the behaviour I expect:
- When reconnectedTeams takes no more than 5 - 10 seconds to realise there's a viable network connection, and reconnect.
- When I send messages whilst disconnected I don't expect Teams to whinge about it and fail to send the message: I expect it to automatically send the message when it reconnects. I know Teams is an IM client but some sense of asynchronicity is fine: I want to be able to fire and forget, not be forced to babysit, especially because when you switch channels you may not realise your last message didn't send, which is *bad* if the message is important.
The desktop app does not reconnect automatically after internet connection is lost and up again. You need to click on "Reconnect" and neither this doesn't work all the times. Only the PC restart solves it. Teams app should reconnect automatically once Internet is up again (like Skype).
Teams is like an app written 20 years ago. This is the modern age when people are mobile... laptops are put to sleep. Wifi switched off on planes etc.
Teams needs to automatically self-reconnect. On Wifi connected, reconnect! So simple.
(And thanks for it being offline all yesterday due to this issue. I really didn't miss those missed calls!)
Hans Hong (dyndragon) commented
Same issue, but in addition even after it seems to have reconnected, the channels are not showing the latest messages. Only way to fix it is to quit the app and relaunch.
John Gruber commented
I think my largest issue is caused by the lack of notification. If the Teams icon in my task bar blinked, or a snackbar popup in the bottom right alerted me of the disconnect I can manually address the problem.
We are having the same issue organization-wide 3000+ computers. It is random and very intermittent. As the network administrator I am getting tickets because it looses "network connectivity" but the computer in whole is online and operational. I have example log files I can submit for review.
It happens on my regular network connection - with better luck through my phone.