# Sessions stuck in In progress

**URL:** <https://community.livekit.io/t/sessions-stuck-in-in-progress/489>\
**Category:** Cloud Dashboard\
**Tags:** agent-development, node-js\
**Created:** [March 7, 2026, 2:50am UTC](https://community.livekit.io/t/sessions-stuck-in-in-progress/489 "2026-03-07T02:50:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ngolitech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/ngolitech/32/611_2.png) [@ngolitech](https://community.livekit.io/u/ngolitech)\
**Post date:** [March 7, 2026, 2:50am UTC](https://community.livekit.io/t/sessions-stuck-in-in-progress/489/1 "2026-03-07T02:50:25Z")

</div>

When I try to delete the room via API, it says no room exists but on dashboard I have one that is showing as active for 6 hours and another one for the past 30 mins. Why do I have these and how to gracefully end them? Also, it would be nice to have the ability to do it directly on the dashboard.

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [March 9, 2026, 9:22am UTC](https://community.livekit.io/t/sessions-stuck-in-in-progress/489/2 "2026-03-09T09:22:10Z")

</div>

Hi, which room ID is this?

These two other issues are relevant:

> [@How to end an active LiveKit room session from the dashboard](https://community.livekit.io/t/how-to-end-an-active-livekit-room-session-from-the-dashboard/128):
>
> This question originally came up in our Slack community and the thread has been consolidated here for long-term reference. How can I end an active LiveKit room session from the dashboard?

> [@Wrong data presented in session](https://community.livekit.io/t/wrong-data-presented-in-session/401/3):
>
> In these sort of cases, the cli can be assumed to be more reliable. I also see some other similar reports and the team are working on a fix. As CWilson says, you will not be charged for this duration, and the figure will eventually be corrected by our reconciler in the event of these spuriously long rooms.

---

<div class="post-metadata">

**Author:** ![ngolitech](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/ngolitech/32/611_2.png) [@ngolitech](https://community.livekit.io/u/ngolitech)\
**Post date:** [March 25, 2026, 4:33pm UTC](https://community.livekit.io/t/sessions-stuck-in-in-progress/489/3 "2026-03-25T16:33:10Z")

</div>

Ran into this issue again this morning.

**LK CLI says:** All 10 rooms return `not_found`. `lk room list` shows zero active rooms.

**LK Cloud dashboard says:** 7 of those rooms show **ACTIVE** with “In progress”, durations climbing (52-131 min), 0 participants. Only 2 show CLOSED

for room in  
“dev–pros-moe-b240b1f3-cbe0-42a5-872c-0d51800c52c3”  
“dev–supp-naga-b7de715a-8a2b-40f8-997f-0bdbb42d9fb4”  
“dev–self-internal-e0cdd289-9c32-4aab-ad3d-d0f4f72b70c6”  
“dev–self-internal-ff5faff6-203d-4665-ae37-01b1e68ae04f”  
“dev–self-internal-a3681d54-a604-4600-9598-4a3e6bb85fa4”  
“dev–pros-joe-d3050b70-776b-4bdf-a7fa-b90a255b5c5a”  
“dev–pros-joe-eef20be0-292a-4eeb-8c8d-60f42a9607e7”  
“dev–supp-naga-9cbfc984-92c4-4ce6-be4c-3e1c6c8812dd”  
“dev–supp-naga-e645e00d-1bd3-4f34-b91f-8de72382c751”  
“dev–supp-naga-b21c0a6f-3d7d-4d2e-ae27-e33efbbd0354”; do  
result=$(lk room delete “$room” 2\>&1 | grep -v “WARNING:”)  
echo “$room → $result”  
done

dev–pros-moe-b240b1f3-cbe0-42a5-872c-0d51800c52c3 → twirp error not\_found: requested room does not exist  
dev–supp-naga-b7de715a-8a2b-40f8-997f-0bdbb42d9fb4 → twirp error not\_found: requested room does not exist  
dev–self-internal-e0cdd289-9c32-4aab-ad3d-d0f4f72b70c6 → twirp error not\_found: requested room does not exist  
dev–self-internal-ff5faff6-203d-4665-ae37-01b1e68ae04f → twirp error not\_found: requested room does not exist  
dev–self-internal-a3681d54-a604-4600-9598-4a3e6bb85fa4 → twirp error not\_found: requested room does not exist  
dev–pros-joe-d3050b70-776b-4bdf-a7fa-b90a255b5c5a → twirp error not\_found: requested room does not exist  
dev–pros-joe-eef20be0-292a-4eeb-8c8d-60f42a9607e7 → twirp error not\_found: requested room does not exist  
dev–supp-naga-9cbfc984-92c4-4ce6-be4c-3e1c6c8812dd → twirp error not\_found: requested room does not exist  
dev–supp-naga-e645e00d-1bd3-4f34-b91f-8de72382c751 → twirp error not\_found: requested room does not exist  
dev–supp-naga-b21c0a6f-3d7d-4d2e-ae27-e33efbbd0354 → twirp error not\_found: requested room does not exist

 ![lk_incorrect_active_rooms](https://us1.discourse-cdn.com/flex001/uploads/livekit2/original/1X/8ddeb3f7486526c563255bbb28508dc544614775.png)

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [March 26, 2026, 9:31am UTC](https://community.livekit.io/t/sessions-stuck-in-in-progress/489/4 "2026-03-26T09:31:17Z")

</div>

I struggled to find those rooms, but then I noticed that the double hyphen has been autocorrected to a single en dash, so “dev–self-internal-ff5faff6-203d-4665-ae37-01b1e68ae04f“ is actually `dev--self-internal-ff5faff6-203d-4665-ae37-01b1e68ae04f`.

Not sure if this happened when you were copying the question, or before you fed it to the CLI, but if the latter, it would explain why the rooms were not found.