Hi LiveKit Support Team,
I wanted to report a UI bug I encountered in the LiveKit dashboard today.
I noticed that one of my sessions (RM_XZYnWzNX7Fms) was showing as ACTIVE on the Sessions list page with a continuously increasing duration counter (it reached 184+ minutes). However, when I clicked into the session detail page, it clearly showed the session had already ended at 7:29:26 PM on May 25, 2026, with a total duration of only 2 minutes.
Details:
- Project: ophelia-voice-agent
- Session ID: RM_XZYnWzNX7Fms
- Room Name: sbx-cyz89z-aEcds5sQss2jxdZjmKLEWc
- Actual Start Time: May 25, 2026, 7:27:55 PM
- Actual End Time: May 25, 2026, 7:29:26 PM
- Actual Duration: 2 minutes
- Sessions list was showing: ACTIVE, 184+ minutes
My concern is whether this discrepancy is purely a UI/caching issue, or if it could affect billing and usage calculations. Could you please confirm that my account is only being charged for the actual 2-minute session duration, and look into why the sessions list is not reflecting the correct closed status?
Thank you for your help.
Best regards
We are also facing same issue. Since yesterday its been over 1000+ minutes for 800+ calls, Session is still showing as active although the rooms were closed under 2 mins.
Sorry @Hamza_Chaudhry @Marvin_Dytianquin @ikya_venus , I also see another report of this today in the community.
There is nothing to be concerned about, and this did not impact billing or functionality.
Fundamentally, this was an increased frequency of this this issue which we see occasionally: Frequently Asked Questions (FAQ) - #18 by darryncampbell
@darryncampbell This issue is happening now again with over 450+ calls got affected so far. Along with this, the emission of the room closed event is getting delayed, which is causing issues with several post-cleanup tasks. Additionally, all delayed room closed events are being emitted simultaneously, leading to multiple issues related to rate limiting. This is currently impacting our production systems. Please look into this urgently.
Sessions that are shown on your dashboard as active should not impact service in any way. We’ll take a look at the caching but the dashboard is not real time.
room closed event is getting delayed…delayed room closed events are being emitted simultaneously, leading to multiple issues related to rate limiting.
What do you mean by this? I don’t see any webhooks associated with the session ID you mentioned above so not sure how they can be delayed.
hello please try changing Quick Ranges from 24hrs to 60 days. the session was closed in that range i think this is more accurate than the 24hrs