I’m seeing what looks like a Cloud UI / indexing inconsistency in project p_3ygejur0ebq.
Summary:
- LiveKit Cloud is clearly receiving and processing our agent sessions.
- Project-level analytics update correctly.
- The agent logs show that the session report was uploaded to LiveKit Cloud.
- But the Sessions page table still shows No results for the same project/time window.
Project and agent:
- Project ID: p_3ygejur0ebq
- Project URL: Sign in | LiveKit Cloud
- Agent ID: CA_pCQrGjpe2r7N
- Current deployed version at time of repro: v20260325152127
- Agent page shows 1 deployed agent and 0 concurrent sessions after the call ends, which is expected
Date/time of repro:
- March 25, 2026
- Roughly 11:23 AM America/New_York
- Deploy completed at about 2026-03-25T15:22:55Z
- Fresh repro call started immediately after that
What we observed before the fix:
- Our agent could remain orphaned in the room after the browser participant disconnected
- This appeared to prevent clean session finalization
What we changed:
- We explicitly linked the session to the joined participant and forced disconnect cleanup
- In Node.js we set:
- participantIdentity: participant.identity
- closeOnDisconnect: true
After that change, behavior improved and the room lifecycle became correct.
Fresh repro after deploy:
- We started a new call from our web app against project p_3ygejur0ebq
- The deployed Cloud agent handled the call
- We ended the call from the app UI
- The agent logs showed the participant disconnect and clean session shutdown
- The room disappeared from LiveKit shortly after
- Cloud analytics updated
- But the Sessions table still showed no row
Concrete room/session details from the repro:
- Room name: wo-note-ff3159e0-db3f-4bd4-8516-329ae83a075c
- Agent job ID in logs: AJ_udoZEzwmejza
- Room ID in logs: RM_y9ALzJM8wWbi
Relevant deployed agent log lines from the successful repro:
- received job request
- closing agent session due to participant disconnect (disable via RoomInputOptions.closeOnDisconnect=False)
- [session-close] event fired, reason: participant_disconnected
- AgentSession closed
- [session-completed] backend notified successfully
- Session report uploaded to LiveKit Cloud
That final line seems especially important:
- Session report uploaded to LiveKit Cloud
What the Cloud UI shows:
- Sessions page top-level metrics are not zero
- Unique participants updates
- Total rooms updates
- Overview page also updates correctly:
- Connection success: 100%
- participant minutes are populated
- data transfer is populated
- platform/country analytics are populated
So the session is definitely being counted in analytics.
But the issue is:
- Sign in | LiveKit Cloud
- selected time window includes the repro
- top counters show the session activity
- yet the table below still says No results
What this does not appear to be:
- not a wrong-project issue
- not an observability-disabled issue
- not a failure to dispatch the agent
- not a session that never reached Cloud
- not a room that stayed permanently active after the fix
Why I believe this is a Cloud-side issue:
- the session report upload is explicitly logged as successful
- aggregate analytics ingest correctly in the same project
- the detailed Sessions list/table does not render the corresponding entry
Request:
- Can you check whether session reports for project p_3ygejur0ebq, especially around room wo-note-ff3159e0-db3f-4bd4-8516-329ae83a075c on March 25, 2026 around 15:23Z, were ingested but not indexed/rendered in the Sessions table?
- If there is a known delay, hidden filter behavior, or a separate prerequisite for table rows beyond what is required for aggregate analytics, please let me know.
Thanks.