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

Support
1

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.

2

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.

3

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