This message was deleted.

cc @bright-dream-51521 @acoustic-engineer-41666

Just a suggestion, but if you want total control over these, you could end them by utilizing the Server SDKs.

Thanks for reporting this. Looking

@brief-refrigerator-69901 Well, this might have happened due to some error on our end during development. Normally, everything is ok 🙂 Thank you

@polite-postman-38647 i’ll look it up, will reach out to you if I need any info

Thank you 🙏

@polite-postman-38647 this bug was related to analytics reporting it falsely as active. The room was actually ended on 5/12 and ran for 6mins. No webhook event was sent now as the room was already closed

Thank you. One more question tho - do you also see if the webhook was sent back then on 5/12? So I know if I should look into our app - because it seems the webhook wasn’t sent at all

@polite-postman-38647 could you check the webhook registered handler for room ended events? These webooks r failing, but all other webhooms r succeeding

Webhook failed with error 500 on getting the ingress list. It seems that the roomName was not properly passed to the function call (picture 1). Unfortunately we haven’t logged the exact response data (picture 2). Anyway, I have updated our code so if there is no roomName, the function won’t be invoked. The interesting thing here is how it could be passed without the roomName, because we get the ingress list like this:

ingressList = await ingressClient.listIngress(event.room?.name);

And in log I see the roomName was part of the event (picture 3)

@polite-postman-38647 Do you still see this error? There were some updates to fix this problem.

cc: @able-gigabyte-21598

cc @chilly-animal-65189

If I understand the above properly, listIngress fails when the roomName is empty? Are you using the JS server SDK? What version?

@eager-zoo-16408 No, I haven’t noticed that anymore (but as I wrote, I have updated the code) @chilly-animal-65189 Yes, that’s what I understood from the logs (screenshots) above. Unfortunately, I have added logging the

response.data

just recently. We’re using

"livekit-server-sdk": "1.1.4"

Thanks

In that case I suppose we can consider this closed. Thank you for your help, guys.

@polite-postman-38647 thank you for your detailed report. We appreciate it! 🙏 And of course, let us know if you run into any other problems.