Teams Live Event - Queue screen fallover

%3CLINGO-SUB%20id%3D%22lingo-sub-1392579%22%20slang%3D%22en-US%22%3ETeams%20Live%20Event%20-%20Queue%20screen%20fallover%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1392579%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20afternoon%2C%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWe%20had%20our%20first%20Teams%20Live%20Event%20on%20Monday.%20The%20system%20worked%2C%20largely%2C%20well.%20However%20around%20half%20an%20hour%20into%20the%20event%2C%20as%20Producer%20I%20found%20that%20the%20Queue%20window%20starting%20to%20freeze%20up.%20I%20would%20select%20a%20source%20to%20Queue%20then%20click%20%22Send%20Live.%22%20From%20the%20recording%2C%20I%20could%20see%20the%20that%20selection%20went%20live%20at%20the%20right%20time%20but%20the%20Queue%20window%20would%20then%20lock%2C%20with%20an%20updating%20circle%20in%20it.%20The%20previous%20source%20would%20still%20have%20the%20Live%20marker%20around%20it%20and%20the%20Send%20Live%20button%20was%20greyed%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETwo%20other%20Producers%20were%20also%20watching%20the%20call%20so%20I%20deferred%20to%20one%20of%20them%20to%20make%20the%20next%20cut%2C%20whereafter%20they%20found%20the%20same%20issue.%20The%20same%20then%20happened%20to%20the%20third%20Producer.%20By%20this%20time%20my%20system%20had%20unfrozen%20but%20it%20happened%20again%20to%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20bulk%20of%20the%20event%20was%20a%20presentation%20which%20went%20smoothly%20however%20the%20problem%20became%20more%20acute%20during%20a%20Q%26amp%3BA%20where%20we%20cut%20between%20the%20main%20presenter%20and%20a%20Q%26amp%3BA%20moderator.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20would%20this%20happen%3F%20Is%20there%20a%20clash%20when%20having%20more%20than%20one%20Producer%20view%20the%20Producer%20panel%3F%20Or%20is%20there%20a%20possible%20connection%20speed%2Fserver%20load%20issue%20which%20might've%20caused%20this%20problem%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EKind%20regards%2C%3C%2FP%3E%3CP%3ERich%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1392579%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ELive%20Events%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1411101%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Live%20Event%20-%20Queue%20screen%20fallover%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1411101%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F668933%22%20target%3D%22_blank%22%3E%40BaldRickB%3C%2FA%3E%26nbsp%3BTeams%20Live%20event%20producer%20limit%20is%20250.%20It%20may%20likely%20a%20connection%20or%20a%20service%20glitch%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-live-events%2Fplan-for-teams-live-events%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fteams-live-events%2Fplan-for-teams-live-events%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1433015%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Live%20Event%20-%20Queue%20screen%20fallover%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1433015%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20info%20-%20I'd%20been%20looking%20into%20this%20question.%20However%20on%20the%20day%20we%20only%20had%207%20Producers%2FPresenters%20in%20the%20Event.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20have%20since%20done%20another%20call%20and%20didn't%20experience%20the%20issue%20so%20I%20suspect%20you're%20right%20-%20something%20fell%20over%20on%20that%20day%20which%20may%20not%20happen%20again.%3C%2FLINGO-BODY%3E
Occasional Contributor

Good afternoon,


We had our first Teams Live Event on Monday. The system worked, largely, well. However around half an hour into the event, as Producer I found that the Queue window starting to freeze up. I would select a source to Queue then click "Send Live." From the recording, I could see the that selection went live at the right time but the Queue window would then lock, with an updating circle in it. The previous source would still have the Live marker around it and the Send Live button was greyed out.

 

Two other Producers were also watching the call so I deferred to one of them to make the next cut, whereafter they found the same issue. The same then happened to the third Producer. By this time my system had unfrozen but it happened again to me.

 

The bulk of the event was a presentation which went smoothly however the problem became more acute during a Q&A where we cut between the main presenter and a Q&A moderator.

 

Why would this happen? Is there a clash when having more than one Producer view the Producer panel? Or is there a possible connection speed/server load issue which might've caused this problem? 

 

Kind regards,

Rich

6 Replies

@BaldRickB Teams Live event producer limit is 250. It may likely a connection or a service glitch
https://docs.microsoft.com/en-us/microsoftteams/teams-live-events/plan-for-teams-live-events

Thanks for the info - I'd been looking into this question. However on the day we only had 7 Producers/Presenters in the Event.

We have since done another call and didn't experience the issue so I suspect you're right - something fell over on that day which may not happen again.

@BaldRickB 

 

We have experienced the same circle spin when queuing up the next person.  This has happened now 3 times over the last month.....including today a meeting with under 10 attendees.  There were not multiple producers and only about 6 participants.  Frustrating, as we had to reschedule the meeting.  We have successfully had Live events for over a year.....this problem is recent to us.

 

Any suggestions?

Hi,

Unfortunately we've had this maybe a dozen more times in the year that we've been using Live Event and we've never found an explanation. It seems to be random and can effect those on good bandwidth as well as those on poorer connections.

For any event we're organising now we put in two producers with clear roles of primary mixer and backup, so that the backup only takes over if requested.

Sorry I can't provide a solution or place to start but I think mitigation of side effects here is the key - have a backup producer (or two) ready to dive in.
The infra is getting better, and you should see much improvement after this week for the similar issue

@Susheel_Dogra   Thank you for the update!