This message was deleted.
# helpdesk
s
This message was deleted.
e
Hey @bumpy-queen-608, there is a limit on “Total concurrent participants” of 100
You can check if you hit it in the Dashboard > Settings > Project > Connection limits
b
Hi @eager-zoo-16408, Thanks for your response. Our project hasn’t hit any limit yet
I found as soon as our meeting duration hit 5 mins, livekit websocket get disconnected and closed the meeting
e
This is not expected. Can you DM me your project ID? I will forward it for internal investigation.
Can you check if you can reproduce the same behavior with Meet? https://meet.livekit.io/?tab=custom
b
We tried it with meet.livekit.io. It doesn’t cause similar issue.
e
@bumpy-queen-608 is there a reason why you set
recorder: true
when generating the token?
cc @polite-kilobyte-67570 @boundless-energy-78552
b
We are simply just want to indicate the meeting is being recorded.
Let us set to false and re-test again
e
That would be great 👍 @boundless-energy-78552 suspects:
Yes my guess is that if recorder is true, the room will autoclose because the SFU thinks there is no participant inside it
👍 1
1
d
When the meeting is being recorded with LiveKit Egress,
Room.isRecording
will automatically flip to true. Our recording stack is built by having a new participant join the session with
recorder: true
grant.
🙌 1
1
that grant should not be used by normal participants
1
🙌 1
b
Thanks team for your prompt support. Yes, setting
recorder: true
cause the issue of meeting disconnect after 5 mins.
🙌 3