Host is using the web client
One limitation of the Zoom web client is that it currently doesn't support prompting the host for local recording permission. This means that if the host is using the web browser version of Zoom, the bot won't be able to prompt the host and capture the meeting.
How to fix: The host should switch to using the Zoom Desktop app (on Windows, Mac, or Linux).
Host was not present
Sometimes the Notetaker joins a meeting but is unable to capture because it never asked for permission. This occurs when the host was not present in the meeting, and thus was unable to grant recording permissions to the bot.
How to fix: We recommend that the host of the Zoom meeting will be in attendance. If this is not conducive to your workflows, reach out to [email protected] for assistance.
The host's computer recording setting is disabled
If the host's global setting for computer recording is disabled, the bot will fail to capture the meeting.
In this case, the bot will have a Recording Permission Denied event with a zoom_local_recording_disabled Sub Code.
How to fix: Make sure the host enables their global user-level computer recording setting in their Zoom user settings. Adjust this setting by going to https://zoom.us/profile/setting, then clicking on the Recording tab and toggling on "Record to computer files."
The host has disabled permitting participants to record to computer files
In this case, the host has their global computer recording setting enabled, but they can't grant participants permission to capture to computer files, which is needed for the Jump notetaker to record.
The notetaker will emit a Recording Permission Denied event with a zoom_local_recording_request_disabled Sub Code.
How to fix: The host should enable this in their profile settings, under "Who can request host permission to record?" Select both "Internal meeting participants" and "External meeting participants."
The host has disabled requesting recording permission within the current call
If the host has the proper user-level recording settings set up on the Zoom website, but has disabled the option to allow participants to request local recording within the call, the bot will not be able to capture the meeting.
In this case, the bot will emit a Recording Permission Denied event with a zoom_local_recording_request_disabled_by_host Sub Code.
How to fix: The host should enable this setting within the call.
The password for the meeting is not included in the Zoom link
The Notetaker may not be able to enter a meeting if the meeting is passcode-protected and the passcode is not embedded in the Zoom URL.
To determine whether the passcode is embedded in a Zoom URL, check to see if the URL includes "pwd=" followed by a series of letters and numbers.
For example, a Zoom URL with a passcode embedded might look like https://zoom.us/j/100000000?pwd=MMeetotestf9022 instead of https://zoom.us/j/100000000.
To enable Zoom to embed the meeting passcode in the URL by default, do the following:
Sign in to the Zoom web portal.
In the navigation menu on the left-hand side of the page, click on Settings.
Click the Meeting tab.
Under Security, click the Embed passcode in invite link for one-click join toggle to enable it.
If a verification dialog appears, click Enable or Disable to verify the change. Note: If the option is grayed out, it has been locked at either the group or account level. Contact your Zoom admin.
Your passcode-protected Zoom meetings should now have URLs that include "pwd=".
Zoom internal error
On rare occasions, the Notetaker may fail to enter a call with a zoom_internal_error sub code.
Unfortunately this means something went wrong on Zoom's end, and we have limited visibility into the underlying error.
We do our best to handle these errors internally through retries but on rare occasions this error can cause the Notetaker to fail.
If this becomes a recurring issue for a certain situation or user, please let us know and we can raise the issue with Zoom.
Host never received the recording consent popup
In certain cases, a user may report that the notetaker never captured any data and they never received a recording consent popup to grant recording permissions.
When this happens:
The Notetaker will not have a
recording_permission_allowednor arecording_permission_deniedeventNone of the
meeting_participantson the bot will haveis_hostastrue
This is the same situation as the host not being present, but in this case, the end user that created the meeting was actually in the call.
If the host claimed they were present, but no participant is shown as the host, it's likely that the user joined the Zoom call while signed into a different Zoom user than the one that created the meeting.
How to fix: Ensure the host joins Zoom meetings from the same account that they used to create the meetings.
If the end user needs to support granting recording permissions from various Zoom accounts, they can assign their alternative account(s) as alternative hosts.