We are storing a key in our DB for determining if the agent session is active or not. We've had a few records in our DB that stayed marked as active even though they were days old. Currently we are just relying on the "close" event to stop our session pollers and do a final write to the DB updating the insights and marking the session as complete. Is the "close" event the most reliable or should I use a few events to determine if the session is truly ended?

Thanks for reaching out, Brandon. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

Right now I'm calling ctx.shutdown() in my participant_disconnected request if the participant is the user. We also have a tool that hangs up the call, inside this tool call we are manually deleting the room are these reliable ways of handling this or is this prone to error?

Thank you for reaching out! I’d love to help you navigate this. Calling

ctx.shutdown()

in your

participant_disconnected

handler is a dependable way to disconnect the agent, and manually deleting the room is a great approach to make sure the session ends for everyone involved. To make things run even more smoothly, here are a few best practices to keep in mind: • Agent Disconnection: Using

ctx.shutdown()

is perfect for disconnecting the agent while letting other participants stay connected. It also triggers shutdown hooks and ensures the agent process ends cleanly. • Room Termination: When you want to end the session for all participants, using

ctx.delete_room()

or the equivalent API is the way to go. This helps with proper cleanup when the session is truly over. • Race Conditions: Just a heads-up—if the agent and a participant disconnect at the same time, there could be race conditions. The good news is that the

delete_room

API is idempotent, so calling it multiple times won’t cause issues. Still, it’s best to ensure your cleanup logic runs only once. • Awaiting Completion: Don’t forget to await

session.aclose()

before deleting the room. This makes sure all ongoing tasks, like audio or message handling, finish properly. By following these tips, your current approach should work smoothly and reliably when handling session termination. If you have any more questions or need further clarification, feel free to ask—I’m here to help! Sources: Inside a session | LiveKit Docs | Job lifecycle | LiveKit Docs | Agents telephony integration | LiveKit Docs | Agents telephony integration | LiveKit Docs | Inside a session | LiveKit Docs