tall-fountain-87900
12/16/2025, 4:04 PMtall-airline-16756
12/16/2025, 4:04 PMtall-fountain-87900
12/16/2025, 4:05 PMtall-airline-16756
12/16/2025, 4:06 PMrecord=True / relevant agent-start parameter or your egress start API/CLI call).
2. Check Analytics/Session data: see the session’s egress value (0 = never started, 1 = active, 2 = ended).
3. Verify project/platform settings: ensure Egress is enabled for the project and the Egress service is running (self-host or cloud setting).
4. If this session had only 1 participant, confirm your agent/egress startup logic doesn’t depend on participant count or other runtime conditions.
5. Check agent observability hooks/logs (transcripts/traces) to confirm the agent was invoked and recording was requested.
If you want, share:
• The Room/Session ID shown in the dashboard row,
• The code snippet where you start the session/egress or enable agents,
• The session egress value from the Analytics API (if available).
I can then point to the exact field to inspect or spot missing code calls. Would you like to share those details?
Sources: Self-hosting the Egress Service | LiveKit docs | Rooms, participants, and tracks | LiveKit docs | Analytics API | LiveKit docs | Streamline Troubleshooting with Agent Observability | Observability data hooks | LiveKit docs