Cloud session stuck ACTIVE while RoomService says room does not exist

Cloud Dashboard
1

Hello,

We have a LiveKit Cloud session that appears stuck as ACTIVE in the Sessions dashboard and its duration keeps increasing.

Project ID: p_5spev44i5ey
Project name: Play-space
LiveKit host: play-space-kv6jbrcl.livekit.cloud
Session ID: RM_Rd5hu8thRBJ7
Room name: alpha-2
Started at: Apr 24, 2026, 1:14:16 AM
Dashboard status: ACTIVE
Dashboard duration: over 5,000 minutes and still increasing
Participants shown: 1
We verified that the key used by Vercel belongs to this same LiveKit Cloud project.

We verified that this is the same project/key used by our hosted Vercel app.

RoomService API results with this key:

  • listRooms([“alpha-2”]) returns []
  • listRooms() returns []
  • deleteRoom(“alpha-2”) returns: “requested room does not exist”

We also checked our local browser/process state and do not see an active connection to LiveKit Cloud. Current local dev is connected to localhost LiveKit only.

Analytics API is unavailable on our current plan:
“scale plan or higher is required”

Could you please terminate or correct this stuck session/accounting entry? If this session is still counting against quota, it is consuming quota for a room that RoomService no longer sees.

This looks similar to this report:

Also, could you please restore the quota consumed by this stuck ACTIVE session, or confirm that the stuck duration is not counted against our Build plan quota? The dashboard shows this session running for thousands of minutes after RoomService no longer sees the room, so we need the quota/accounting corrected as well.

2

This is almost certainly a stale/orphaned dashboard session record, not an active room that can be controlled with the RoomService API. Reboot your dashboard.

You shouldn’t post any part of your API key publicly. You might want to edit that out.

3

Thanks for the quick reply, and good point about the API key. I removed it from the post.

The stuck ACTIVE session has disappeared now, and LiveKit joins seem to be working again.

I’m still not sure how to interpret the Billing page. It currently shows:

  • Build included WebRTC participant minutes: 5,000 min
  • Additional WebRTC participant minutes: 1,611 min
  • Total shown for April: 6,611 min

Does this mean the stale session still counted toward our monthly usage, or is this just historical usage that won’t affect the Build plan quota going forward?

For context, the stale session was RM_Rd5hu8thRBJ7. It had been shown as ACTIVE for thousands of minutes even though RoomService returned no rooms and deleteRoom(“alpha-2”) returned “requested room does not exist”.

4

You do not pay for room duration. It is only participant minutes.