Skip codes for unrecorded calls

BAD_SCHEDULE

The meeting did not start at the planned time and so the Gong bot was unable to join. This probably happened when the meeting was moved close to the planned start time (after the Gong bot was dispatched).

CALL_BLACKLISTED

The meeting was blacklisted because it contains a blocked email, domain, or phrase.

CALL_PROVIDER_DISABLED_FOR_COMPANY

The meeting was scheduled with a web conferencing or telephony provider that was then disabled for your company before the meeting started.

CAN_NOT_LISTEN_IN

The call did not have VOIP, which is set by the organizer.

CANCELED_BY_OWNER

The host cancelled the recording using the Stop recording action on the Gong homepage.

CANCELLED

The calendar event was moved or updated, for example, cancelled via the calendar, or deleted or rejected by the organizer.

CANNOT_CONNECT_ERROR

The Gong bot was unable to get into the meeting for a technical reason, such as, because the Zoom meeting required a version upgrade, or the Webex meeting had a redirect URL.

COMPLIANCE_ENFORCING

The meeting didn't comply with the recording consent settings, and therefore the call was not recorded.

For example, this can happen when the consent page was changed to be enforced after the meeting was scheduled, and the meeting does not use the consent page link.

COMPLIANCE_SYSTEM_DECISION

Compliance with the consent settings is enabled, but we were unable to verify that the meeting complied with the settings, and therefore did not record the meeting.

COMPLIANCE_USER_REQUEST

A participant exercised their right to not be recorded when joining the meeting.

In other words, a participant clicked the "Join but don't record" option when going through the consent page.

CONNECTOR_WAS_NOT_APPROVED

The Gong bot was not admitted to the meeting.

DENIED_ENTRY

The Gong bot was actively denied entrance to the meeting.

DID_NOT_START

Gong logged a "waiting for the meeting to start" notification, but the meeting never started.

DUPLICATE

Two meetings were scheduled to start at the same time, and Gong recorded the second meeting.

For example, this can happen when:

ENDED

The meeting ended before or when the Gong bot joined.

HAS_DO_NOT_RECORD_USERS

One of the participants is set to "never record".

HOST_NEVER_SHOWED

Gong logged a "waiting for the host to start the meeting" notification, but the meeting never started.

IMPORT_FROM_CUSTOMER_URL_FAILED

We were unable to import the recording from the given URL.

This skip code appears when Gong attempts to import a call via API.

IMPORT_FROM_DIALER_FAILED

We were unable to import the recording from the telephony system provider.

INACTIVE_HOST

The meeting host was deactivated in the web conferencing provider.

INTERNAL_MEETING

Internal meetings are not recorded, as per your company recording settings.

INVALID_MEETING_URL

Either the meeting URL had no meeting information, or the URL is invalid.

KICKED_OUT

The Gong bot was removed from the meeting soon after the start time.

MEETING_IS_FULL

The Gong bot couldn't join the meeting because it reached the maximum number of participants.

MISSING_RECORDING

Gong was unable to retrieve the call from the provider that recorded it.

This can happen when the recording was deleted.

N/A

We identified an unexpected, unclassified failure in recording.

NO_ATTENDEES

The meeting started, but no other attendees joined.

NO_COMPANY_PARTICIPANTS

The meeting started, but nobody from your company joined. We left the meeting, and disregarded the recorded portion.

NO_CONTENT

The call was processed but we didn't find any usable audio or video.

NO_SHOW

The Gong bot joined the meeting, but nobody else came.

NOT_FROM_ORGANIZER_CALENDAR

The meeting wasn't organized by a recorded team member, and only meetings organized by recorded team members get recorded, as per your company recording settings.

OBSOLETE_CALL

The meeting was organized within 20 minutes of the start time, and Gong did not manage to scan the calendar and pick up the need to record in time.

This can be avoided by manually adding the Gong bot.

OVERLAPPING_MEETING

Two meetings were scheduled at the same time, and Gong recorded the second meeting.

PASSWORD_REQUIRED

The Gong bot couldn't join the meeting because a password was required to enter.

PMI_UNMATCHED_TIMES

The start time of the meeting didn't match the calendar event. This can happen when you have many back to back meetings using the same personal meeting link.

RECORDING_STOPPED_BY_HOST

Zoom was recording the meeting natively, and the recording was stopped by the host close to the start.

STOP_USER_REQUEST

Recording was stopped via the homepage.

If using native Zoom recording, you should see a short recording in Zoom cloud storage, unless you have Delete recordings initiated by Gong but not retrieved enabled, in which case we will have deleted the recording from Zoom.

TEMP_CANNOT_CONNECT_ERROR

Gong attempted to join the meeting but there was a temporary error that prevented us from connecting, for example, timeout.

TOO_LONG

The call was too long for processing.

The maximum recording length we can process is 6 hours.

TOO_SHORT

The call was too short for import, as per your company recording settings.

UNKNOWN_MEDIA

The recording's media file type was not recognized, and so we couldn't process the imported file.

You can try to convert the file to a standard MP4 file, and reimport it.

USER_RECORDING_OFF

The meeting host's data capture was removed after the meeting was scheduled.

WEB_CLIENT_DISABLED

The Gong bot was unable to join the call because participants were not allowed to join via web browser in the meeting settings.

The Gong bot cannot join meetings where the provider app must be used.