5-09-16 16:06:11,258 - ERROR livekit - livekit::rt...
# ask-ai
f
2025-09-16 160611,258 - ERROR livekit - livekit:rtc enginertc session787livekitrtc engine:rtc_session - Subscriber pc state failed {"room": "68c8cdb35960b35a2023299d", "pid": 64559, "job_id": "AJ_oREEMAsoHkRi"} 2025-09-16 160611,259 - WARNING livekit - livekit:rtc engine453livekit:rtc_engine - received session close: "pc_state failed" UnknownReason Resume {"room": "68c8cdb35960b35a2023299d", "pid": 64559, "job_id": "AJ_oREEMAsoHkRi"} What is this error?
t
Thanks for reaching out, Mok. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
It looks like the error
Subscriber 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