fierce-jordan-44682
09/16/2025, 8:06 AMtall-airline-16756
09/16/2025, 8:06 AMtall-airline-16756
09/16/2025, 8:07 AMSubscriber pc state failed and the log message received session close: "pc_state failed" UnknownReason Resume are pointing to a hiccup in the subscriber's WebRTC peer connection, often caused by network disruptions or connectivity glitches. When this happens, LiveKit steps in with a recovery mechanism that tries an ICE restart to get the connection back on track.
If the ICE restart works, the session can continue with just a little interruption. But if it doesn’t, LiveKit might need to do a full reconnection, which means disconnecting and rejoining the session—this can be a bit more noticeable.
These processes are built to automatically handle those temporary network bumps, but if you’re seeing persistent or more serious issues, it might be worth digging a bit deeper. Please feel free to reach out if you'd like help troubleshooting any specific connectivity challenges or if you want to understand more about how these recovery steps work—I’m here to help!
Sources: Docs::Home | Connecting to LiveKit | LiveKit Docs | pkg/rtc/participant.go | lib/src/core/engine.dart | livekit/src/rtc_engine/rtc_session.rs