Skip to main content
Flow diagram showing recording, transcript, summary, insights, and drafts as separate processing outputs. Do not treat a meeting as one all-or-nothing state. Ergo can have a recording ready while transcript, summary, insights, drafts, or reporting are still pending.

State types to keep separate

  • Recording state: whether media was captured and stored.
  • Transcript state: whether transcript segments are available.
  • Summary state: whether a meeting summary or generated note is ready.
  • Insight and reporting state: whether reporting fields or rubric outputs have been computed.
  • Draft state: whether post-call emails or follow-ups were generated.
  • Desktop processing state: desktop recordings can show processing, completed, completed_no_transcript, or failed.

What to do while processing

  • Wait for the specific output you need instead of retrying everything immediately.
  • Refresh the meeting list or detail page after a few minutes.
  • For desktop recordings, a processing card can appear before the completed meeting record is ready.
  • Use retry only where the UI exposes retry for the failed output.

When to escalate

  • The recording is missing after the bot was admitted and recording.
  • The transcript is empty or failed for a meeting with meaningful audio.
  • A desktop recording remains failed.
  • A required draft or reporting output is missing after the meeting has a transcript.
Last modified on June 8, 2026