That’s great to hear that managing the state locally is working! I’ll be happy to help if there are any issues with using this approach.
I was able to follow up internally on this and discovered that we would not be able to implement a change to prevent this callback from being triggered multiple times. This originates from the back end service, and was initially implemented to overcome some edge cases with the Zoom client. So basically, preventing duplicate events from being sent could break the Zoom client.