Participant remains visible for 4–5 minutes after leaving a meeting in Meeting SDK Web 6.1.0

Meeting SDK
1

We are developing an application using Zoom Meeting SDK for Web version 6.1.0.

The application joins Zoom meetings through a browser controlled by Puppeteer.

If the recording permission dialog is not approved within a specified period, our application clicks the “Leave Meeting” button through Puppeteer to leave the meeting.

However, in some cases, even though the browser has already left the meeting, the participant remains visible in the participant list on other users’ Zoom desktop clients for approximately 4–5 minutes.

Could you please confirm the following?

  • Is this expected behavior or a known specification of Zoom or the Meeting SDK?
  • Could this be an issue with the Meeting SDK or Zoom client?
  • What is the recommended method to ensure that leaving the meeting is reflected promptly for other participants?
  • Should we use a Meeting SDK API to leave the meeting instead of clicking the leave button through Puppeteer?
  • Are there any known workarounds, settings, or logs that we should check for this behavior?

Environment:

* Zoom Meeting SDK for Web: 6.1.0
* Browser automation: Puppeteer
* Other participants: Zoom desktop client
* Delay before the participant disappears: approximately 4–5 minutes

We can provide the meeting ID, timestamps, SDK logs, and browser console logs if required.

Thank you for your assistance.

2

Use the SDK method directly instead of automating the button. For Client View, call ZoomMtg.leaveMeeting with confirmation disabled and handle its success and error callbacks. For Component View, call client.leaveMeeting. You should keep the browser context alive until the leave operation reports success.

One useful check is to log timestamps for the leave-method invocation, its success or error result, and Puppeteer’s page-close action. If no success result arrives before the page closes, the SDK teardown is being interrupted.

For a managed approach to joining and recording meetings, Recall.ai’s Meeting Bot API handles the meeting lifecycle without Puppeteer automation.

3

Thank you for the detailed guidance.

We will update the implementation to use the SDK leave method directly and keep the browser context alive until the success or error callback is received.

We will also add timestamped logs for the SDK leave call, its result, and the Puppeteer page-close action to verify whether the SDK teardown is being interrupted.

Thank you also for sharing the information about Recall.ai. We will take a look.