Thanks — I’m looking into why you’re seeing duplicate room events. Below are the most common causes and the concrete steps you can take to stop or mitigate duplicates. Acknowledging your question: you asked why LiveKit is sending duplicate room events. Here are likely reasons and what to do for each. 1) Webhook retries (at-least-once delivery) • Cause: LiveKit retries deliveries until it receives a successful response. Slow responses, timeouts, or server crashes after processing cause retries to look like duplicates. • Fix: Return a fast

200 OK

immediately after validating the request; process the event asynchronously. 2) No idempotency on consumer side • Cause: LiveKit may deliver the same event more than once; the receiver must handle duplicates. • Fix: Persist

event.id

(or a payload hash) in a short-lived store (Redis) and ignore repeats for that id. 3) Multiple subscribers/listeners for the same events • Cause: You may have the same room events delivered via multiple paths (e.g., webhooks + server SDK listeners) or multiple services configured to receive the same webhook. • Fix: Ensure a single delivery path per event type or route webhooks into a single queue/topic with one consumer group. 4) Multiple workers/processes dispatching the same resource queue • Cause: Per-room resource queues can be picked up by more than one worker if not coordinated, causing duplicate processing. • Fix: Coordinate workers (single consumer per queue) or centralize webhook intake behind a message broker. 5) Improper signature verification or replayed/spoofed events • Cause: If you aren’t verifying the webhook signature, you might accept replayed/spoofed payloads that look like duplicates. • Fix: Verify the HMAC signature with your API secret before processing. 6) Room name reuse / lifecycle issues • Cause: Re-creating rooms with the same name too quickly can create ambiguous events. • Fix: Use unique room IDs or avoid immediate reuse of room names. If you’d like, tell me: • Are you receiving these duplicates via webhooks, SDK event listeners, or both? • Do you see the same

event.id

in duplicates (if available)? • Is your webhook endpoint returning

200 OK

quickly, or do you have logs showing retries? Give me one of those details and I’ll suggest targeted changes (example code for quick 200 ack + async processing, or idempotency snippet). Sources: examples/survey | livekit/livekit_composite | DeepWiki | server-sdk-ruby | livekit/livekit_composite | DeepWiki | Server-side | livekit/livekit_composite | DeepWiki | Avoiding Room ID Reuse When Re-Creating Rooms With the Same Name