Hello,
I’m experiencing an issue with LiveKit in my development environment: all my test sessions remain in the ACTIVE state indefinitely, even after the tests are completed.
lk room list returning empty is the decisive test, and it means these are not real sessions.
@darryncampbell (LiveKit staff), on a thread with identical symptoms:
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.
And on billing:
The reported usage will not count towards your plan minutes, and will not incur overcharge.
So your not_found on delete is correct, not a failure. The rooms are gone; only the Sessions rows are stale.
Two things to rule out:
- If
LIVEKIT_URL,LIVEKIT_API_KEYorLIVEKIT_API_SECRETare set in your shell, they overridecli-config.yaml,so you may be querying a different server
than the dashboard. Unset them and re-run. - Copy room names from the dashboard rather than retyping. One report traced a failed delete to a double hyphen autocorrected into an en dash.
Still empty after that? Nothing to clean up, and only support can clear the rows.
If lk room list ever does show the room, it is real and something is not shutting down. Fix that server-side: session.shutdown() plus delete_room_on_close=True.
What @abidullahcs.uk has said is 100% correct, but having looked into your sessions, this does look like something on our side rather than yours. Just to emphasise his point that this would not have an impact on your bill.
Only engineering can clear the rows 
I am discussing with them internally.
Update on this, we have posted to the status page:
To re-iterate, there is no billing impact & apologies for the inconvenience.