MS Teams crashes when I manage breakout rooms

%3CLINGO-SUB%20id%3D%22lingo-sub-2102796%22%20slang%3D%22en-US%22%3EMS%20Teams%20crashes%20when%20I%20manage%20breakout%20rooms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2102796%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20been%20an%20organizer%20of%20large%20MS%20Teams%20meetings%20(50-75%20participants)%20for%20delivering%20sessions.%26nbsp%3B%3CBR%20%2F%3ERecently%20(Jan%202021)%2C%20I%20incorporated%20the%20function%20of%20Breakout%20Rooms%20in%20the%20session.%20However%2C%20when%20dealing%20with%20a%20room%20of%2050%20participants%2C%20I%20faced%20the%20following%20problems%3A%3C%2FP%3E%3CP%3E1)%20Starting%20and%20closing%20breakout%20rooms%20is%20extremely%20slow%20(5%20mins)%2C%20often%20freezes%20which%20means%20half%20of%20the%20participants%20are%20back%20in%20the%20main%20room%20while%20other%20half%20is%20still%20stuck%20in%20their%20respective%20breakout%20rooms.%26nbsp%3B%3C%2FP%3E%3CP%3E2)%20While%20closing%26nbsp%3B%20breakout%20rooms%2C%20MS%20Teams%20hard%20crashes%20and%20automatically%20logs%20me%20out.%20Have%20to%20restart%20the%20application%20to%20get%20back%20in.%26nbsp%3B%3C%2FP%3E%3CP%3E3)%20While%20managing%20one%20such%20session%2C%20stopped%20receiving%20chats%2Fmessages%20on%20my%20side.%20Even%20though%20the%20message%20was%20delivered%20by%20the%20sender.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20these%20issues%20relate%20to%20the%20size%20of%20the%20room%3F%20Any%20issues%20with%20the%20workload%20on%20my%20application%20due%20to%20this%20size%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAssistance%20is%20highly%20appreciated%20%3A)%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%26nbsp%3B%3C%2FP%3E%3CP%3ESanmit%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2102796%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2104660%22%20slang%3D%22en-US%22%3ERe%3A%20MS%20Teams%20crashes%20when%20I%20manage%20breakout%20rooms%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2104660%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F944981%22%20target%3D%22_blank%22%3E%40SanmitPardeshi%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20had%20similar%20issues.%20It%20is%20slowish%20to%20start%20the%20rooms%2C%20but%20always%20fails%20on%20closing%20them.%20It%20either%20hangs%20on%20%22closing%22%20on%20all%20the%20rooms%20or%20--%20once%20--%20all%20rooms%20showed%20red%20text%20that%20said%20%22Failed%22.%20Only%20way%20out%20is%20to%20restart%20app.%20Participants%20stay%20in%20their%20rooms%20while%20this%20is%20happening.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi there, 

 

I have been an organizer of large MS Teams meetings (50-75 participants) for delivering sessions. 
Recently (Jan 2021), I incorporated the function of Breakout Rooms in the session. However, when dealing with a room of 50 participants, I faced the following problems:

1) Starting and closing breakout rooms is extremely slow (5 mins), often freezes which means half of the participants are back in the main room while other half is still stuck in their respective breakout rooms. 

2) While closing  breakout rooms, MS Teams hard crashes and automatically logs me out. Have to restart the application to get back in. 

3) While managing one such session, stopped receiving chats/messages on my side. Even though the message was delivered by the sender. 

 

Do these issues relate to the size of the room? Any issues with the workload on my application due to this size? 

 

Assistance is highly appreciated :) 

 

Thanks, 

Sanmit 

5 Replies

@SanmitPardeshi 

I have had similar issues. It is slowish to start the rooms, but always fails on closing them. It either hangs on "closing" on all the rooms or -- once -- all rooms showed red text that said "Failed". Only way out is to restart app. Participants stay in their rooms while this is happening.

@classicmds 

Exactly what happened with me. Still looking for possible explanation :( 

@classicmds Same here :( Last week I thought it was just a coincidence but when that happened again today (twice), I don't longer think it is "just a coincidence". Would love a solution as I will be meeting with those people for 4 more weeks and would rather not face the same issue over and over again :(

Same issue for me, any explanations/solutions?

Sure wish we had some insight into what is causing this, @Microsoft_Teams_team.