# (Urgent) Two open sessions stuck without ending, Unable to test and build product at all due to this blocker

**URL:** <https://protoface.discourse.group/t/urgent-two-open-sessions-stuck-without-ending-unable-to-test-and-build-product-at-all-due-to-this-blocker/69>\
**Category:** Support\
**Created:** [August 8, 2026, 6:38pm UTC](https://protoface.discourse.group/t/urgent-two-open-sessions-stuck-without-ending-unable-to-test-and-build-product-at-all-due-to-this-blocker/69 "2026-08-08T18:38:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nethmin\_Seneviratne](https://yyz2.discourse-cdn.com/flex034/user_avatar/protoface.discourse.group/nethmin_seneviratne/32/16_2.png) [@Nethmin\_Seneviratne](https://protoface.discourse.group/u/Nethmin_Seneviratne)\
**Post date:** [August 8, 2026, 6:38pm UTC](https://protoface.discourse.group/t/urgent-two-open-sessions-stuck-without-ending-unable-to-test-and-build-product-at-all-due-to-this-blocker/69/1 "2026-08-08T18:38:34Z")

</div>

Two sessions stuck in ending for 21+ hours, holding all plan concurrency  
▎  
▎ Plan: Starter (2 concurrent). Both slots are occupied by sessions that will not finish ending, so no new session can start.  
▎  
▎ - sess\_01KZEZVEKZJ5CPGAQGV5SA2BF3 — created 2026-08-07T20:50:20Z, ended\_at 2026-08-07T20:50:38Z  
▎ - sess\_01KZEAGRFJ45A2QZCE5HSDYJW4 — created 2026-08-07T14:37:30Z, ended\_at 2026-08-07T14:38:20Z  
▎  
▎ Both have status: “ending” with ended\_at already populated. GET /v1/sessions?status=active still returns both, and POST /v1/sessions returns 429 quota\_exceeded / concurrent\_sessions.  
▎  
▎ Re-issuing POST /v1/sessions/{id}/end returns 200 with status: “ending” and changes nothing. DELETE /v1/sessions/{id} returns 405. GET /v1/status reports all components operational.  
▎  
▎ Please clear these two sessions. Also: is ending intended to count against the concurrency cap, and is there a timeout that eventually releases it? A session that hangs in ending currently takes a slot permanently with no client-side remedy.

---

<div class="post-metadata">

**Author:** ![proton](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@proton](https://protoface.discourse.group/u/proton)\
**Post date:** [August 8, 2026, 8:15pm UTC](https://protoface.discourse.group/t/urgent-two-open-sessions-stuck-without-ending-unable-to-test-and-build-product-at-all-due-to-this-blocker/69/2 "2026-08-08T20:15:46Z")

</div>

Hi Nethmin, thank you for flagging this. Our team has manually resolved your sessions, and we are investigating a fix to prevent the same error for others.

---

<div class="post-metadata">

**Author:** ![proton](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@proton](https://protoface.discourse.group/u/proton)\
**Post date:** [August 9, 2026, 2:49am UTC](https://protoface.discourse.group/t/urgent-two-open-sessions-stuck-without-ending-unable-to-test-and-build-product-at-all-due-to-this-blocker/69/3 "2026-08-09T02:49:40Z")

</div>

Hi Nethmin, our team has deployed a permanent fix for this issue. Thank you again for the detailed report.