Meetings Troubleshooting

Symptom: "No meeting-bot provider is configured. Set one up in Settings → Integrations."

Cause: No provider (Vexa or Recall) has base URL/API key saved yet, so Start Bot and Pull Transcript refuse to run.

Fix: Have a System Manager complete the Meeting Bot settings page, then retry.

Symptom: "Unrecognized meeting URL (expected Google Meet, Zoom, or Teams)."

Cause: The URL isn't a supported platform link.

Fix: Paste the full Meet/Zoom/Teams meeting URL exactly as shared.

Symptom: Bot fails to join with a BAD_GATEWAY error

Cause: The provider rejected or failed the start request — the message shown is the provider's own error.

Fix: Check the provider's API key/base URL in settings and the meeting's waiting-room/permissions settings, then try Start Bot again.

Symptom: "This meeting has no bot session to poll." / "no transcript yet."

Cause: Pull Transcript needs a platform + native meeting id from a bot session; Extract needs stored transcript text. Manual transcripts have no bot session.

Fix: For manual transcripts use Extract directly; for bot meetings wait for recording to finish, then Pull Transcript first.

Symptom: "No create permission for tasks" when applying review action items

Cause: Creating tasks from accepted action items requires tasks create on top of meetings edit.

Fix: Get tasks create access, or apply with only the next-step update (leads/deals only) and create tasks manually.

Symptom: A teammate's pending draft never shows on your dashboard

Cause: Pending-review lists filter out meetings whose linked record you can't read instead of leaking them; own-scope also hides meetings you didn't create.

Fix: Ask for read access to the linked record (and all-scope meetings if appropriate).

Was this helpful?

YesNo