Hi

Thanks for reaching out, benjamin222. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.

Livekit session events for a room is empty, with the only event being "Room ended". However, I was able to pick up the call. How is this possible?

Thanks — I’m responding about why your room’s session events are empty except for the single "Room ended" event even though you could join the call. Two likely causes: • Livestream (skip-subscriber-broadcast) mode: if the room was in livestream mode, participants who are only viewers/subscribers do not generate participant events (only publishers do). That can make your event list appear empty while the call still connects. • Webhook delivery/retries: webhooks are push-based and not guaranteed; transient delivery failures, a slow or failing webhook endpoint, or retries falling behind can cause missed or delayed events. LiveKit will retry transient failures, but missing deliveries can leave gaps. What I need to narrow this down: • Was the room created in livestream mode (are participants split into publishers/viewers)? • Your room ID and project ID (or full webhook event payloads/timestamps) so I can check whether events were sent and whether there were delivery failures or retries. If you prefer, share a sample webhook payload or the time you joined and I’ll look for matching events and delivery status. Sources: Livestream Mode, with interactive elements

Was there a livekit outage today? If so is that why the webhook delivery failed

Thanks — I can’t confirm an outage from here. To determine whether LiveKit had an outage or if webhook delivery failed, please share the following so I can investigate: • Project ID (or API key/unique identifier) and the Room ID. • Approximate timestamps (with timezone) when you joined the call and when you expected webhook events. • Your webhook endpoint domain and whether your receiver showed errors or high latency at those times. • Any webhook delivery logs you have (response codes, timestamps, retry attempts) or the raw webhook payloads you received (if any). • Whether the room used livestream / skip-subscriber-broadcast mode (were participants publishers or viewers?). • SDK/platform used (Web, iOS, Android, server) and any client logs or errors. If you don’t have logs immediately, please check your webhook receiver access/error logs and the LiveKit status page (status.livekit.io) for incident notices, then share whatever you find. Once I have those details I’ll check event delivery and retry history. , with interactive elements

May 28, 2026, 103350 AM EST

Thanks — I’ll check the May 28, 2026 103350 AM EST timeframe for you. To investigate whether an outage or webhook delivery issue affected that room, please provide any of the following you can share: • Project ID and Room ID (or a meeting/room name). • Your webhook endpoint domain and any webhook receiver logs (response codes, timestamps, retry attempts) around 103350 AM EST. • Whether the room was running in livestream / skip-subscriber-broadcast mode. • SDK/platform used (Web, iOS, Android, server) and whether the participant who joined was publishing tracks or only viewing. If you don’t have those immediately, check your webhook receiver logs and the LiveKit status page (status.livekit.io) for incidents at that time and tell me what you find. I’ll use whatever you provide to look up event delivery and retry history. , with interactive elements