Skip to content

Help

Known Limitations

Understand the current alpha's meeting, scheduling, synchronization, and notification boundaries.

New meetings, not existing-event registration

Section titled “New meetings, not existing-event registration”

GC Zoom creates scheduled meetings. There is no feed option to select an existing meeting, register attendees for one, or register webinar attendees. Adding an invitee supplies an email address to a newly created meeting; it does not create an individual registration URL.

Each processed feed creates its own meeting for an entry. A form with two matching feeds can create two meetings.

GC Zoom does not check calendar availability, prevent overlapping meetings, or reserve appointment slots. Form date and time values become meeting details, not availability checks.

The optional update/delete behavior sends entry changes to Zoom. Changes made in Zoom do not flow back to the entry. Switching connected accounts does not transfer existing meetings.

Meeting creation uses the WordPress site timezone. There is no timezone selector per feed or attendee in the current settings UI. Tell users which timezone the form expects.

The immediate form confirmation may render before the meeting exists. Use notifications for join links. A failed initial processing attempt can release a notification without a URL while retries remain pending.

Preset durations are currently resolved as form field IDs, not literal minute counts. This can produce the 30-minute fallback or an unintended value from a field. Verify the actual meeting duration in Zoom. See Duration.

Conditional feeds and delayed notifications

Section titled “Conditional feeds and delayed notifications”

The notification delay counter includes active feeds even when conditional logic prevents them from processing. A skipped feed can leave a notification containing {gcz_meeting_url} waiting indefinitely. See Notification timing.

Plugin deletion does not erase saved tokens

Section titled “Plugin deletion does not erase saved tokens”

Deactivating or deleting GC Zoom leaves its saved Zoom access and refresh tokens in the WordPress database. Disconnect each account in Forms → Settings → GC Zoom → Zoom Accounts before deleting the plugin. Disconnecting a single feed is not enough. See Disconnecting and removing GC Zoom for removal steps and details about retained Zoom data, form data, and backups.

Connecting GC Zoom does not remove Zoom’s account permissions, administrator policies, or plan limits. Test with the account and meeting configuration you intend to use.