mirror of
https://github.com/suitenumerique/meet.git
synced 2026-08-05 16:37:43 +00:00
lebaudantoine
f6cdb1125b
Instead of relying on the egress_started event—which fires when egress is starting, not actually started—I now rely on egress_updated for more accurate status updates. This is especially important for the active status, which triggers after egress has truly joined the room. Using this avoids prematurely stopping client-side listening to room.isRecording updates. A further refactoring may remove reliance on room updates entirely. The goal is to minimize handling metadata in the mediator class. egress_starting is still used for simplicity, but egress_started could be considered in the future. Note: if the API to start egress hasn’t responded yet, the webhook may fail to find the recording because it currently matches by worker ID. This is unstable. A better approach would be to pass the database ID in the egress metadata and recover the recording from it in the webhook.