Skip to content

Help

Troubleshooting

Diagnose account authorization, missing meetings, incorrect times, and empty join links.

  • Allow pop-ups for your WordPress admin site and try again.
  • Sign in to the Zoom account that should create the meetings.
  • If your organization restricts third-party apps, ask your Zoom administrator whether the connection is approved.
  • Check Forms → Settings → GC Zoom for account issues, and reconnect the affected account.

After reconnecting, confirm that the correct account is selected on the form’s feed and save it.

  1. Open the form’s Settings → GC Zoom. Confirm the feed is active and its conditional logic matches the submission.
  2. Check that the entry is not marked as spam.
  3. Confirm the feed has a connected account and that it is still authorized.
  4. Open the entry and inspect its feed status and error notes.
  5. Check Forms → Settings → GC Zoom for connection issues.
  6. Review scheduled actions under Tools → Scheduled Actions, searching for gc_zoom. Meeting work is asynchronous, and failures can schedule retries.

If the entry has no inserted meeting, its GC Zoom feed section can show Process Feed. Check Zoom and any pending scheduled actions before processing manually, so you do not unintentionally repeat an operation whose outcome is uncertain.

GC Zoom logs processing errors and retries failed operations. Persistent creation failures can also produce a GC Zoom Feed Error email to the WordPress administrator. Do not assume a retry succeeded without checking the entry and Zoom.

  • Check Settings → General → Timezone in WordPress.
  • Map Start Date directly to the Date field, and Start Time to the Time field.
  • Use YYYY-MM-DD when entering a custom fixed date.
  • Check the submitted values, not just the labels in the form editor.
  • Remember that an empty start date uses the submission date and time. A date without a time schedules the meeting at midnight.

Submit a new test entry after changing the feed. Editing the feed alone does not update meetings already created from older entries.

  • Make sure the message contains {gcz_meeting_url} exactly.
  • Check that the entry’s active feed has successfully created a meeting.
  • Confirm the account remains connected and can retrieve that meeting from Zoom.
  • Review errors from the first processing attempt: delayed notifications can be released after a failed attempt, before a retry succeeds.

The tag can return an empty value when there is no accessible meeting. If creation later succeeds, verify the link and send a follow-up notification as needed. See Notifications and Merge Tags for the timing details.

Check whether any active Zoom feed was skipped by conditional logic. In the current alpha, notification-delay counting includes those feeds even though they do not process. This can leave the notification waiting indefinitely. See Known Limitations.

Check Update & Delete Records on the feed. It must be enabled for entry edits to update a meeting. The entry must already have an associated meeting, and its account connection must remain available.

If the problem persists, submit a support ticket to Gravity Wiz. Support hours are Monday–Friday, 9 am–5 pm Eastern Time, as listed on our support page.

Include the plugin version, affected form and entry IDs, relevant error messages, and whether the meeting exists in Zoom. Choose an email address you can receive replies at so the team can follow up on your ticket. Do not send access tokens, passwords, or private meeting links in public reports.

You can also browse the Gravity Wiz documentation and scope of support.

Follow both parts of Disconnecting and removing GC Zoom: remove the app in Zoom App Marketplace, then disconnect the account in WordPress. If the app is not listed in Zoom, check which account you used to authorize it or ask your Zoom administrator. If the WordPress connection remains after removal in Zoom, disconnect it from Forms → Settings → GC Zoom → Zoom Accounts; Marketplace removal does not delete the stored WordPress credentials.