Thanks — I’m responding to your question about how long it takes for session info to update in LiveKit. Session information is updated asynchronously and there isn’t a single fixed latency number. LiveKit delivers updates via events (for example,

room_metadata_changed

and

participant_metadata_changed

) and aims for eventual consistency across the system. However, propagation time can vary depending on factors like network latency and whether participants are connected to SFU nodes in different geographic regions. What to do to handle updates reliably: • Use event listeners (e.g., listen for

room_metadata_changed

/

participant_metadata_changed

) instead of polling properties immediately after making a change. • Expect eventual consistency — plan your UI/logic to tolerate short delays or reconcile state when you receive the event. If you’re seeing unusually long delays, tell me: • which metadata or session field is updating, • whether clients are in different regions, and • an example of the delay you’re observing (approximate seconds). I can suggest targeted troubleshooting steps based on those details. Sources: Handling asynchronous metadata updates in LiveKit | LiveKit | How We Built a Globally Distributed WebRTC Mesh Network