Symptoms
- A recording exists but the transcript, notes, or summary are missing.
- The transcript exists but insights, drafts, or reporting fields are missing.
- A desktop recording is stuck in processing, failed, or not uploaded.
- The meeting appears in one source but not on the expected Ergo page.
Most common causes
- Recording, transcript, summary, insights, reporting, and drafts process separately.
- The bot did not join, was not admitted, or was removed before useful capture.
- The source provider or desktop app did not deliver the recording/transcript asset.
- The meeting failed upload or processing.
- The meeting did not qualify for downstream insights, reporting, or drafts.
What to check
- Check the meeting source, bot status, and processing status.
- Confirm whether the missing output is recording, transcript, summary, insights, reporting, or drafts.
- Wait for separate outputs to finish when one asset is still processing.
- Use retry where the UI exposes it for failed uploads or processing.
- Confirm the viewer has access to the meeting and expected output.
Resolution steps
- If the bot never joined, resolve the meeting-capture issue before investigating output processing.
- If the recording exists but transcript/summary is missing, check processing state and retry where available.
- If desktop upload failed, retry upload/processing from the UI path that exposes the failed recording.
- If drafts or reporting are missing, confirm the meeting qualifies and the relevant integrations/access are configured.
When to contact support
- Contact support when the meeting was captured, the source asset is ready, access is correct, and a specific output remains missing.
- Include the workspace, affected user, meeting title or ID, source, missing output type, processing state, and approximate time window.
- Keep examples generalized and avoid sharing sensitive customer content in support requests.