Skip to main content
Content generation starts after you end a session. A slow note is not always a failed session. On Partner APIs, calling content endpoints before status is completed returns empty or incomplete results. On Mobile SDK, wait for session events before you fetch content.

Common causes (Mobile SDK)

From Mobile SDK troubleshooting FAQs:
  • Long session (more audio to process)
  • Poor audio quality
  • Network issues during upload
  • High server load
  • Large session context or metadata

Partner API

After you end an ambient session, generation is async. Closing the WebSocket and a successful REST end do not mean the note is ready. Poll Get ambient session status until status is completed, then call content APIs. Stop on skipped, failed, or aborted. Flowchart: End ambient session, GET /status, Status?, Call content APIs, Stop and handle. Flowchart: End ambient session, GET /status, Status?, Call content APIs, Stop and handle. See Wait for Ambient before fetch.

Mobile SDK

1

Watch Session Events

Use session delegate events for generation progress and failure. Show a progress state while processing continues.
2

Check Network and Capture

Confirm the device can upload. Record in a quieter place and keep the mic clear when quality is poor.
3

Retrieve After Ready

Wait for generation completion events before you fetch content. Processing still running is not the same as failure.

Next steps

Wait for Ambient before fetch - Poll status until completed Empty or incomplete notes after ending an ambient session - Retrieve only after generation finishes Mobile SDK troubleshooting FAQs - Content generation delay causes Offline upload failures on Mobile SDK - Upload before generation can finish Get ambient session status - Status values for polling
Last modified on October 27, 2026