The warning message you encountered,

signal client closed: \"stream closed\"

, indicates that the WebSocket connection used for signaling between the client and the LiveKit server was unexpectedly closed. This is categorized as a SIGNAL_CLOSE disconnect reason. When this occurs, LiveKit's built-in recovery mechanisms automatically activate: • Automatic Reconnection: The client attempts to resume the session by reconnecting to the server. • Message Queuing: Outgoing messages are queued during reconnection to prevent data loss, and these are flushed once reconnection is successful. • Fallback Connection: If the primary connection fails, the system tries to connect using fallback region URLs. The system also maintains connection health through a ping/pong mechanism, and if reconnection is successful, the room state (including published and subscribed tracks) is typically preserved. If you are experiencing persistent issues or need further assistance, please provide additional details about the context in which this warning occurred, such as the SDK being used, the frequency of the issue, or any specific steps to reproduce it. Sources: livekit-api/src/signal_client/signal_stream.rs | protobufs/livekit_models.proto | packages/livekit-rtc/src/proto/participant_pb.ts | livekit-android-sdk/src/main/java/io/livekit/android/events/RoomEvent.kt | lib/src/proto/livekit_models.pbenum.dart