Thanks — I looked at the events you shared. You're seeing the meeting stop because the room was closed (a

ROOM_CLOSED

participant leave followed by

Room ended

). When a room becomes empty of regular participants, LiveKit will close it by default, which disconnects any remaining actors (egress/agents). Likely causes: • The room hit an

empty_timeout

and was automatically closed. • The room was explicitly deleted via the DeleteRoom API. What I need to narrow this down: • How are you creating the room? (show the create-room request or parameters, especially

empty_timeout

if set) • Do you call DeleteRoom anywhere in your server code after participants leave? • Are there background agents/recording egress that should keep the room alive? If so, how are those clients authenticating/joining? With those details I can tell you which of the two causes fits and give exact steps to keep the meeting running (for example: increase or disable

empty_timeout

, ensure agent/egress joins as a regular participant, or stop calling DeleteRoom). Sources: Server lifecycle | LiveKit docs | Avoiding Room ID Reuse When Re-Creating Rooms With the Same Name