Session and room remains active even no room or agent deployment

Hello LiveKit Team,

I found an active session from April in my LiveKit Cloud account and would like to understand its current status.

Here are the details:

  • Room: Tells_Room_e53b114b76a048de97f8b9283a938d11
  • Room Session ID: RM_nfdNC8VcmWYe
  • Start Time: April 17, 2026, 18:42:05

This room was originally created using LiveKit Cloud, and I am using the Python SDK.

My concern is that the session still appears to be Active and shows two participants connected. However, when I search for the room in the LiveKit Cloud console, I cannot find it.

image

It’s also strange that this active session shows a duration of 3 minutes, even though April was two months ago.

image

When I open the session, the duration is listed as nearly 70,000 minutes, but the total WEBRTC participant minutes is 0 seconds.

I also see the “Delete Room” event in the session events. That means the room shouldn’t actually exist anymore, right?

I can’t figure out why this session is still open, or rather, why the session still exists. As it stands, my agent isn’t running locally or in the cloud.
Could you please take a quick look at this and let me know what you find? It doesn’t really bother me right now, but I just want to make sure there isn’t a bug, or at least let you know about it.
Oh, and I waited the full 24 hours, and nothing has changed.

I’m going to deploy a different agent today so I can work on a project. If it gets in the way of solving the problem, I’ll be happy to take it down again.

Best regards

This is a zombie session the room is already deleted (confirmed by the “Delete Room” event in your session history), the dashboard just hasn’t synced it. File a support ticket with session ID RM_nfdNC8VcmWYe to get it cleared. Ref:

I can confirm this is a dashboard display issue. The CLI is accurate, if it’s returning no active rooms, then that is more reliable.

Oh, and I waited the full 24 hours, and nothing has changed.

Thanks, from context clues you’ve already seen this FAQ:

This has been raised internally as an ongoing frustration (that the dashboard is occasionally inaccurate), and it is being escalated.

I’m going to deploy a different agent today so I can work on a project. If it gets in the way of solving the problem, I’ll be happy to take it down again.

Please do go ahead, there is no effect on anything other than dashboard display