participantRoleChanged not triggering

[Harsh246]

I have deployed a Docker image of Jitsi on my own infrastructure for video conferencing needs. While utilizing the Jitsi Meet External API, I have been sporadically facing problems with the “participantRoleChanged” event failing to fire at seemingly random occasions.

Specifically, when a participant’s role is changed during a conference, the event works as intended most of the time, triggering my event listener registered through the API’s EventEmitter interface. However, without any discernible pattern, the event arbitrarily fails to propagate through the External API, even though I can verify in the JavaScript console logs that it’s not firing internally within the Jitsi client.

I have tried debugging to find potential causes but have been unable to determine what is specifically causing this inconsistent behavior with the participantRoleChanged event in my self-hosted environment. The workflow appears to match the documentation, and it works correctly more often than not, but appears to randomly stop surfacing the event to the API listener.

I’m unsure if it could be related to my Docker deployment architecture, concurrency issues, or something else happening behind the scenes. I would greatly appreciate any insights from the Jitsi development team on what could explain this seemingly sporadic failure of the participantRoleChanged event to trigger through the External API. Please let me know if any other troubleshooting details would be helpful in resolving this problem.

[Harsh246]

@saghul can you please provide any input in this?

[saghul]

What image versions are you running, and how do you know the event was internally fired?