Troubleshoot scans and episode generation

Most problems in the meeting flow resolve with one targeted retry. This article maps what you see to what to do.

The scan failed

If the scan step shows a red "Scan failed" message, the details in the message usually point at the storage connection. Go back to the details step and press Save & rescan to run it again, or use Rescan files from the meeting page. If the message mentions storage being unavailable, the documents service was unreachable at that moment and a retry after a minute typically succeeds. If it keeps failing, check the Connections page for the state of your documents import.

No files were suggested

An empty suggestions list means nothing in storage matched the meeting closely. Sharpen the inputs: a specific title and, above all, meeting goals give the scan its strongest signals. Also check the time window chips, because a 30 day window excludes everything older. You can always pick files manually from All other files.

An episode failed

Each episode fails or succeeds on its own. A failed episode shows its error on the meeting page while the others play normally. To retry, run the generation again: open the meeting, use Rescan files, confirm the file selection, and press Create podcast. Every episode is re-rendered, but your workspace is only billed for episodes beyond what the meeting already billed, so a retry that fixes one failed episode bills at most that one.

If the meeting itself shows Failed with "All episodes failed to generate", something systemic interrupted the run, most often a temporary provider issue. Retrying later usually clears it, and support can check the run's logs if it persists.

Some selected files were ignored

The generator can only use files it can read as text. Files with unsupported formats and files whose text extraction comes back empty, such as a scanned image-only PDF, are skipped silently and the briefing is built from the rest. If a critical document is a scan, upload a text-based version. If none of the selected files could be read, the meeting fails with "None of the selected files could be read as text."

Audio is missing but the script is there

Every episode is generated with audio, so an episode that plays silently, or that shows a note about audio being skipped, is a fault on our side. There is no setting in Quorum that turns audio on or off, so there is nothing for you or your admin to change and nothing to re-run. The transcript stays complete and readable in the meantime. Tell us and we will pick it up, and we will let you know once the episode has been regenerated.

The meeting will not accept changes

Meeting details cannot change once the podcast is generating or completed, and the file selection can only change while the meeting is in review. This is by design, so the generated briefing always matches the reviewed inputs. Use Rescan files on a completed or failed meeting to reopen the flow.

The meeting disappeared

If a meeting page reports it could not be found, the meeting was deleted or you are no longer one of its attendees. Deleting a meeting mid-generation is safe: the run is cancelled cleanly and nothing further is billed.

Live updates seem stuck

The meeting page updates over a live connection and falls back to polling every 15 seconds when the connection drops, so progress still flows on a flaky network. If a page has clearly stalled, a reload is safe at any point. No action in the flow is triggered by simply viewing it.