https://livekit.io logo
Join Slack
Powered by
why am I getting this error in my worker log, - ER...
# ask-ai
w
why am I getting this error in my worker log, - ERROR asyncio - Unclosed client session, whenever I disptach the agent explicity to a room?
t
Thanks for reaching out, Arthur. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
The error "ERROR asyncio - Unclosed client session" usually pops up when a session isn’t closed properly in your code. No worries though—here are some friendly tips to help you fix it: • Make Sure to Clean Up Sessions: Use 
await self.session.aclose()
to close the session properly before your worker moves on. • Keep an Eye on the Close Event: You can add an 
on_close
event handler in your 
AgentSession
to catch and log when the session closes. Here’s a quick example:
Copy code
@session.on("close")
def on_close(ev: CloseEvent):
    print(f"Agent Session closed, reason: {ev.reason}")
• Remember to Await in Function Tools: When you’re using function tools to close the session, make sure to use 
await
inside the function. Like this:
Copy code
@llm.function_tool
async def close_session(self):
    await self.session.generate_reply(instructions="say goodbye to the user")
    await self.session.aclose()
• Skip Background Tasks for Closing: It’s better to close the session directly within the right context instead of using background tasks. If you want, you can share the specific code that’s giving you trouble, and I’d be happy to help you troubleshoot it! Sources: livekit-agents/livekit/agents/ipc/job_proc_lazy_main.py
w
I thought the session will be automatically closed, once the last non agent participant leaves, and there was no need for an explicit call to the close function?
t
You’re absolutely right! LiveKit does automatically close sessions when the last non-agent participant leaves the room. When that happens, the room will close, and any agents still connected will be disconnected automatically. So, there’s no need to worry about calling the close function yourself in this situation. Sources: Worker lifecycle | LiveKit Docs | Anatomy of an Agent | LiveKit Docs | Anatomy of an Agent | LiveKit Docs | Inside a session | LiveKit Docs
w
So what can be causing that error?
t
The 'Unclosed client session' error can pop up for a few reasons, so let’s walk through them together: • Server-Initiated Closure Without Proper Handling: Sometimes LiveKit might close the session (like when a room is deleted or a participant is removed), and if the client doesn’t handle the 
Disconnected
event properly, the session could stay open. • Improper Manual Closure: If you’re using 
session.aclose()
but forget to await it correctly, it might leave sessions hanging. • Inactivity Detection Failures: If the system that detects inactivity isn’t working as expected, idle sessions might not close on their own. • Unrecovered Errors During Session: If an error happens that can’t be recovered from and cleanup isn’t done properly, the session could remain open. To fix this, double-check that you’re handling Disconnected events properly, make sure session.aclose() is awaited as it should be, review your inactivity detection logic, and take a look at your error handling to confirm everything is cleaned up nicely. If you need a hand with any of this, just let me know! Sources: Connecting to LiveKit | LiveKit Docs | livekit-plugins/livekit-plugins-google/livekit/plugins/google/beta/realtime... | Agents Core Architecture | livekit/livekit_composite | DeepWiki | Events and error handling | LiveKit Docs
w
Elaborate on the Disconnected evetn
t
The Disconnected event in LiveKit happens when the connection to the room drops. It gives you a heads-up on why it happened, like DuplicateIdentity or RoomDeleted. This event works across different SDKs, including JavaScript, Rust, Flutter, and Python. Here’s a friendly guide on how to handle it smoothly: • Listen to the Event: Just attach a handler to the 
Disconnected
event on the 
Room
object. This way, you can log the reason and keep your app updated. • Update the UI: Make sure to remove any disconnected participants from the UI and gently let users know what’s going on. • Perform Cleanup: Don’t forget to unpublish tracks, reset any variables, and get everything ready in case you want to reconnect. Example (JavaScript):
Copy code
const room = new Room();
room.on(RoomEvent.Disconnected, (reason) => {
    console.log('Disconnected:', reason);
    // Update UI and handle disconnection
});
Also, keep in mind related events like ParticipantDisconnected (when someone else leaves) and Reconnecting (when the app tries to reconnect). These can really help make the experience smoother when network hiccups or intentional disconnects happen.
Open in Slack
PreviousNext
Powered by