Agent Room not deleted

Agents
,
1

can you explain this

—API.DeleteRoom
9 Feb 2026, 21:26:58—Room ended
9 Feb 2026, 21:26:58agent-AJ_mGKdEmgEbeQY
Participant left (ROOM_CLOSED)
9 Feb 2026, 21:26:57chat_user_8489
Participant left (CLIENT_INITIATED)
9 Feb 2026, 21:26:34chat_user_8489
Participant active
9 Feb 2026, 12:16:14agent-AJ_mGKdEmgEbeQY
Participant active
9 Feb 2026, 12:16:14chat_user_8489
Participant resumed
9 Feb 2026, 12:16:13agent-AJ_mGKdEmgEbeQY
Participant resumed
9 Feb 2026, 12:16:13agent-AJ_mGKdEmgEbeQY
Participant resumed
8 Feb 2026, 21:17:34agent-AJ_mGKdEmgEbeQY
Participant resumed
7 Feb 2026, 20:14:15chat_user_8489
Participant resumed
7 Feb 2026, 05:28:36agent-AJ_mGKdEmgEbeQY
Participant resumed
7 Feb 2026, 05:19:16chat_user_8489
Participant active
7 Feb 2026, 02:04:26chat_user_8489
Participant joining
7 Feb 2026, 02:04:26chat_user_8489
Participant left (DUPLICATE_IDENTITY)
7 Feb 2026, 02:04:26chat_user_8489
Participant active
7 Feb 2026, 02:04:15agent-AJ_mGKdEmgEbeQY
Participant active
7 Feb 2026, 02:04:07agent-AJ_mGKdEmgEbeQY
Participant resumed
7 Feb 2026, 02:04:06chat_user_8489
Participant resumed
7 Feb 2026, 02:04:06agent-AJ_mGKdEmgEbeQY
Participant resumed
7 Feb 2026, 00:52:57

chat_user_8489
Participant resumed
7 Feb 2026, 00:52:29agent-AJ_mGKdEmgEbeQY
Participant active
6 Feb 2026, 23:15:50agent-AJ_mGKdEmgEbeQY
Participant joining
6 Feb 2026, 23:15:50chat_user_8489
Participant active
6 Feb 2026, 23:15:49chat_user_8489
Participant joining
6 Feb 2026, 23:15:49—Room created
6 Feb 2026, 23:15:49

2

Are you self-hosting LiveKit server?
If you are using LiveKit cloud, I could look at our server logs, but I’d need a bit more detail about what the issue is?

3

its livekit cloud , we have inactivity tracker if there is no user activity within 5 mints , it automatically delete the room but i can see there are few sessions like this that i have mentioned early which gives almost 1000mints
session id is RM_6qLPDw8Wtp2F
please let me know if you required further details

4

I struggled to find it, but that session ID is from the 6th - 9th of February so I can’t see any backend logs for that.

If you look at the event logs on the dashboard for that session, the room doesn’t get closed until 9th Feb, which I presume is from your inactivity tracker, but before that, the same participant has multiple joining / resumed events so I’m not sure what is going on.

5

hmm , can you check this one in logs RM_RAWAgJKHNpXs , this session is on 18 march and showing 220mints , but according to our settings i dont see how its happening, and this behviour is causing additional bill.

6

You have chat_user_1508 leaving the room at 02:05:42 and then chat_user_977 joining the room at 02:05:50 (my timezone - the hour doesn’t matter). I think what happened here is you reused the room name, chat_room_4702 and because there was only a few second between one user leaving and another user joining, the system assumed this was all part of the same room, so also reused the same session (room) ID, RM_RAWAgJKHNpXs.

7

i got this, but still the question is how could room be lived for this long time when there is no activity in room
room created at 18 Mar 2026, 07:05:01 chat_user_1508 left at **18 Mar 2026, 02:05:42.949 then another user try to join and rejoin , then there is no activity from 7 to 10 .

this is what we track to prevent room being active when there is no msg**
INFO] virtual-assistant: Added to transcript - role: assistant, preview: ['Hi there! How can I help you today? Are you interested in learning about our AI customer support s
[DEBUG] virtual-assistant: Agent state changed: speaking → listening
[INFO] virtual-assistant: Inactivity: 40s silence detected, sending first follow-up
[DEBUG] virtual-assistant: Agent state changed: listening → speaking
[DEBUG] transcription-service: Added conversation item: assistant - 4 total items
[INFO] virtual-assistant: Added to transcript - role: assistant, preview: [‘Are you still there?’]
[DEBUG] virtual-assistant: Agent state changed: speaking → listening
[INFO] virtual-assistant: Inactivity: 30s after first follow-up, sending second
[DEBUG] virtual-assistant: Agent state changed: listening → speaking
[DEBUG] transcription-service: Added conversation item: assistant - 5 total items
[INFO] virtual-assistant: Added to transcript - role: assistant, preview: [‘I am here to help you.’]
[DEBUG] virtual-assistant: Agent state changed: speaking → listening
[INFO] virtual-assistant: Inactivity: 30s after second follow-up, ending session
[DEBUG] virtual-assistant: Agent state changed: listening → speaking
[DEBUG] transcription-service: Added conversation item: assistant - 6 total items
[INFO] virtual-assistant: Added to transcript - role: assistant, preview: [“It looks like you’re no longer available. Thank you, goodbye!”]

8

I am just looking at the list of events for the session, at the bottom of your dashboard at Sign in | LiveKit Cloud

  1. Room is created and chat_user_1508 joins
  2. chat_user_1508 is in the room until they leave, then 8 seconds later chat_user_977 joins
  3. Several instances of chat_user_977 leaving, then rejoining after a few seconds.
  4. chat_user_977 continues to show strange connection behaviour until the room is eventually closed after they leave a few hours later

I’m not sure what is going on with chat_user_977, it looks to me as though they got stuck trying to reconnect to the server. I’m not really able to tell just by looking at the server logs, it might be enlightening if you had client logs available for that time period.