7 Hour Timeout for Session Host

[ShadowPeak1]

Is there some legitimate reason the product is now enforcing a 7-hour timeout on sessions for the session host?  Ever since a recent update the session software will simply close for me the presenter precisely 7 hours after the session is started (no message about the session ending), even if I am sharing my screen and in the middle of presenting.  Session was created for 8 hours of time initially and it is rather annoying to be kicked off after 7 (right on the dot), some sessions do actually last longer than 7 hours in the real world...really! 

Version 0.104.9, this seemed to have started about 2-3 weeks ago.  Everyone else remains in the session just fine, as the instructor/presenter/organizer I am the only one that is kicked off and then can rejoin and continue.  Most recent training ID where this occurred: 995-156-988.  I can provide plenty more.

[KateG]

Hi @ShadowPeak1 welcome to the Community, thanks for checking us out.  I don't know of a situation where the presenter would be removed from the meeting and there is not a 7-hour timeout. This is not the experience you should be having. We have asked our team for further insight, but you may also want to try contacting customer support and they will review your account. 

[ShadowPeak]

I didn't say I was removed from the meeting, I said my meeting interface suddenly closes with no input from me.  When I restart the software and reconnect to the meeting all attendees are still there and I see two of myself.  One is greyed out (which I excuse) and the other one was created when I reconnect.  The meeting software just closes with no message indicating what happened at all, sometimes when I am in the middle of talking and sharing.  Would be nice to have some diagnostics explaining what is happening instead of just closing itself, looks to be a client software issue.  Internet connectivity is solid, I'm on it constantly 10 hours a day and it never blips.

[KateG]

@ShadowPeak thanks for the clarification. You can report these instances when they occur by following the instructions in Glenn's post here. This will help our team review specific technical issues.