<@U08CKJH7C12> We are facing unique issue in some ...
# agents
a
@refined-appointment-81829 We are facing unique issue in some of our calls, where livekit room reconnecting with below error and after that no agent response comes out resulting in bad experience to user with no agent response to user. 1. what may be route cause of this issue? 2. Any way to handle such scenarios? 3. This occurs rarely? how to reproduce such issues ? so that we can give fix to it. note: we are using livekit-agents==1.2.15 version. livekit==1.0.12 room id: pool-room-bebd5dba-4440-489c-809c-d2d495faf564
Copy code
2025-11-19 21:36:26.710	
{"message": "livekit::rtc_engine:453:livekit::rtc_engine - received session close: \"signal client closed: \\\"ping timeout\\\"\" UnknownReason Resume", "level": "WARNING", "name": "livekit", "pid": 460, "job_id": "AJ_h4g3NTZidJ6M", "timestamp": "2025-11-19T16:06:26.709669+00:00"}
	2025-11-19 21:36:26.710	
{"message": "livekit::rtc_engine:729:livekit::rtc_engine - resuming connection... attempt: 0", "level": "ERROR", "name": "livekit", "pid": 460, "job_id": "AJ_h4g3NTZidJ6M", "timestamp": "2025-11-19T16:06:26.710306+00:00"}
Copy code
2025-11-19 21:36:26.710	
2025-11-19 16:06:26 [info]: [LiveKitRoomPoolManager] :large_yellow_circle: Room reconnecting: pool-room-bebd5dba-4440-489c-809c-d2d495faf564
@lively-winter-88668 any solutions for above issue ?
r
@lively-winter-88668 and I took a look at the logs for that call and see that the client was having connectivity issues and got disconnect from the room. In that case agent left and when client came back agent was not available anymore.
a
Thanks @refined-appointment-81829 and @lively-winter-88668 for checking. Is this due to network connectivity problem ? 2. we also see that sometime livekit room connected back properly, but we some sync issues where TTS audio not playing fully to user after reconnecting. Seeing below errors. Do you think after reconnecting do we need to any additional settings to connect all services like TTS/STT/LLM so that it will run smoothly ?
Copy code
WARNING:livekit: livekit::rtc_engine:453:livekit::rtc_engine - received session close: "signal client closed: "ping timeout"" UnknownReason Resume

2025-11-20 21:58:25,747 - WARNING livekit - livekit::rtc_engine:453:livekit::rtc_engine - received session close: "signal client closed: "ping timeout"" UnknownReason Resume {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

ERROR:livekit: livekit::rtc_engine:729:livekit::rtc_engine - resuming connection... attempt: 0

2025-11-20 21:58:25,748 - ERROR livekit - livekit::rtc_engine:729:livekit::rtc_engine - resuming connection... attempt: 0 {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

WARNING:livekit.agents: _SegmentSynchronizerImpl.resume called after close

2025-11-20 21:58:53,936 - WARNING livekit.agents - _SegmentSynchronizerImpl.resume called after close {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

WARNING:livekit.agents: _SegmentSynchronizerImpl text marked as ended in capture text, rotating segment

2025-11-20 21:58:54,880 - WARNING livekit.agents - _SegmentSynchronizerImpl text marked as ended in capture text, rotating segment {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

WARNING:livekit.agents: _SegmentSynchronizerImpl.end_text_input called after close

2025-11-20 21:58:54,881 - WARNING livekit.agents - _SegmentSynchronizerImpl.end_text_input called after close {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

WARNING:livekit.agents: _SegmentSynchronizerImpl audio marked as ended in capture audio, rotating segment

WARNING:livekit.agents: _SegmentSynchronizerImpl.end_audio_input called after close

2025-11-20 21:58:55,953 - WARNING livekit.agents - _SegmentSynchronizerImpl audio marked as ended in capture audio, rotating segment {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

2025-11-20 21:58:55,954 - WARNING livekit.agents - _SegmentSynchronizerImpl.end_audio_input called after close {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}

WARNING:livekit.agents: _SegmentSynchronizerImpl.playback_finished called after close

2025-11-20 21:58:56,098 - WARNING livekit.agents - _SegmentSynchronizerImpl.playback_finished called after close {"pid": 88215, "job_id": "AJ_ofrJP5FMtpoo"}
l
Yes, around that time in the logs I see a lot of messages related to reconnection and lost packets so it looks like connectivity issues. It looks like the connection had continual issues throughout the duration of the call.
a
@lively-winter-88668 will this livekit cloud connectivity issue results in failing to resume some of the connections like TTS audio doesnt play after reconnection ? We observed TTS audio not playing fully or having echo after reconnection