Describe the bug
When attempting to stop a quick meeting, the system displays a modal saying, "A quick meeting is already started," with options to continue or stop. If the stop button is pressed, two entries appear in the media library instead of one.
To Reproduce
Start a quick meeting.
Attempt to stop it.
Observe the modal with options to continue or stop.
Press "Stop" and check the media library.
NOTE : I saw this occur only once. Seems related to some async fetch for session API
Expected behavior
Pressing the stop button should correctly terminate the quick meeting without generating duplicate entries in the media library caused by a forced double click on the "Stop" button.
Additional context
Seems related to how the front-end "knows" that a quick meeting (session) is already processing. Maybe we shall change routes to ensure a correct await of the quick meeting session to actually end.
Describe the bug
When attempting to stop a quick meeting, the system displays a modal saying, "A quick meeting is already started," with options to continue or stop. If the stop button is pressed, two entries appear in the media library instead of one.
To Reproduce
Start a quick meeting.
Attempt to stop it.
Observe the modal with options to continue or stop.
Press "Stop" and check the media library.
NOTE : I saw this occur only once. Seems related to some async fetch for session API
Expected behavior
Pressing the stop button should correctly terminate the quick meeting without generating duplicate entries in the media library caused by a forced double click on the "Stop" button.
Additional context
Seems related to how the front-end "knows" that a quick meeting (session) is already processing. Maybe we shall change routes to ensure a correct await of the quick meeting session to actually end.