Really annoying as we frequently update a small number of shared spreadsheets, and the convenience of being able to do so directly in Teams is quite lost. I end up just opening in Excel every time to avoid the annoyance.
We are working on a design with more density in mind. Until this design is solidified we are putting this item back to Under Review.
When is this going to ship? The wasted screen real estate, as compared to alternatives such as slack, is a real bug bear for our development teams.
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.