This message was deleted.

Hey Nikola, currently webhooks delivery is at most once. There aren't any retries built in. How are you thinking about using them? We are certainly open to improvements there!

It might be important to know the state of the call. We may want to do some important post-processing after say the ROOM has ended. Easiest way to do so is by relying on ROOM FINISHED webhook, but that webhook may never be received due to some temp network issues or similar. I guess we can’t do much to improve webhooks. If you need them to be very reliable then you should probably use something else, like pooling the Livekit API. Maybe to have some simple retry mechanism, like try to post it few times until you get status 200. Thing is that it would make them a bit more reliable but still probably not enough for critical processes. Long story short, I’m just evaluating at this point. If we figure something out we will post and issue and PR.

I think retries could definitely improve things a bit (for things like temporary blip). But requests can still fail otherwise (network connectivity, extended downtime at destination server). Ultimately, a polling method would be more reliable if those finish hooks require delivery guarantees. Perhaps try

ListRooms

periodically to sync your local state?

A simple bultin retry would be a nice small improvement, if one does care about more event/state - not just room start and finished - polling is not really an option I believe. Retry is a nice boost for robustness.