Troubleshooting Notetaker transcripts, summaries, and the hub

Last updated: November 21, 2026

Available on: Mac, Windows; Mac meeting recording requires macOS 13 or later.

If processing is stuck, a transcript has gaps or wrong names, or Notetaker won't open, follow the recovery steps for your symptom.


Summary or transcript hasn't arrived

  1. Keep Flow signed in and online on the recording device; uploads continue while the computer is locked or idle.

  2. Open the affected meeting's Summary tab in the Notetaker hub.

  3. Follow the action for your message below. You're done when the summary appears without a processing, error, retry or update notice.

While the full summary is being prepared, the Summary tab shows a quick summary with no speaker names; it is replaced by the full summary, so no action is needed. Summaries cover the whole meeting in detail, so longer meetings take longer to appear.

Message

Next action

Summaries appear when a meeting ends / No summary yet

Finish recording first, on every device that's still recording it.

Not auto-generated

Select Generate summary.

Restoring this meeting

No action; wait while the content is brought back to this device.

Waiting for a connection

Reconnect; the meeting finishes on its own, or select Retry processing.

Can't reach our servers to upload this meeting…

Turn off your VPN or switch networks, then select Retry.

Your connection is too slow to upload this meeting…

Select Retry on a faster network; your recording is saved.

Storage full

Free up space on your computer, then select Retry.

We hit a snag processing your meeting

Select Retry processing.

We couldn't process your meeting

No retry is available; contact support.

Update failed. Showing the previous summary.

Select Retry only if offered.

Transcript too short to meaningfully summarize / No meaningful audio recorded

No action; the meeting is finished.

Recovery needs retained usable audio and post-meeting processing turned on; a short or silent meeting or re-run never replaces a real summary you already have. Generate and Retry are unavailable while the meeting is recording or processing, except for Retry during Waiting for a connection and the upload notices above; Retry nudges the existing upload along and never creates a duplicate meeting. If Flow crashes or quits mid-recording, or a stop never completes, the next time you open Flow it finishes the recording and sends it through upload, transcription and summary on its own.

Processing looks stuck or the upload can't get through

Waiting for a connection means your device is offline or has just woken from sleep; the meeting completes on its own once you reconnect, without relaunching Flow and without uploading twice. Errors that happen while you're online are retried for you, and "Servers are busy" means Flow will try again on its own. If a manual retry is declined and a notification says Flow will retry, wait for that retry or the time shown.

A VPN, proxy, firewall or other network block also shows a one-time "Can't upload your meeting. Your network may be blocking it." notification. On a slow connection Flow keeps retrying on its own and the notice stays, so select Retry once you're on a faster network.

With Notetaker Cloud Sync off, meetings stay on your device and are picked up for processing once you turn sync on.

The note shows "Restoring this meeting"

A meeting's notes and summary may not be on this device yet — for example just after you upgrade. Flow fetches the content straight away and the Transcript tab stays unavailable in the meantime. There's nothing to select; the note editor opens on its own as soon as the content is back.

You resumed a meeting that never got a summary

Stop the meeting and check Summary for the completed summary or the next action in the table. Flow uploads the full combined recording — the original plus every resumed segment — and produces a fresh summary. Each stop gets a fresh set of attempts, and the recording stays on your device for the local retention window, so if preparation keeps failing a partial summary can still arrive days later. A resume that captured no new audio closes out with no duplicate summary.

You resumed a meeting that already had a summary

If you haven't edited that summary and the resumed part added enough new audio, Flow uploads the full recording on its own and replaces the short summary and transcript once the complete versions are ready; the earlier summary stays on screen until then. If you edited the summary, Flow keeps your edited version rather than replacing it.

Warning: Local audio is kept for 30 days while a meeting still needs processing, and for two weeks once it is fully processed. When it's deleted, audio-based recovery and resuming end; the meeting, transcript and summary remain. Live, paused and finishing recordings are protected. Deleting a meeting discards its audio, and deleting the transcript also blocks resuming.


The summary is in the wrong language or shows "Auto"

Every summary can be switched to another language — including meetings where no spoken language was identified, which show as Auto and display no language code.

  1. Open the meeting's Summary tab.

  2. Select the language control on the summary toolbar.

  3. Choose the language you want. Flow prepares that summary and shows it when it's ready.

Switching never discards what you had: the first summary stays in the list as Original, so selecting it brings the original wording back at any time.


Missing audio or connection gaps

Your microphone and system audio keep recording through live-transcription outages — including when live transcription never connects — as long as audio can still be saved to your device. Live transcription reconnects on its own and catches up in order once you're back online, and a recording with meaningful audio is kept and processed normally.

Warning: Short gaps can be filled; longer gaps show offline notices, and speech can still be lost in gaps that aren't marked.

Notetaker isn't getting any audio

If your microphone or system audio stops delivering sound — at the start of a meeting or partway through — Flow restarts that source for you. Time you spent muted in the meeting app doesn't count, so muting yourself never triggers the warning. If sound still doesn't return, the Flow Bar shows Notetaker isn't getting any audio with Restart Flow and Dismiss; select Restart Flow to get capture working again.

Your disk is low on space or full

While you're recording, a one-time Storage almost full — About N min of recording left alert appears when your drive has roughly an hour of recording left or less; it is shown even if other tips are muted. Free up space to keep recording. If a stopped meeting doesn't have enough free space to be processed and uploaded, its row in the hub and its note card show Storage full with a Retry button: free up space, then select Retry.

If the disk fills while you're recording, stopping the meeting finishes promptly and reports a storage failure: "Storage Full" means your disk is full, and other save failures show "There was an error". Both notifications offer actions to restart Flow or contact support.

Warning: If saving audio fails during a meeting that was set up for live transcription at the start and not started offline, recording continues with the captured live transcript but no summary refinement. Partial audio saved on your device is discarded; speech captured only in that audio is lost and cannot be recovered by freeing space.

When locally saved audio is the meeting's only capture, including a meeting started offline, the failure stops recording immediately with "Recording stopped because Wispr couldn't save audio to this device." Starting live transcription later does not remove the offline-start exception.

If local audio saving fails at the start, recording continues without summary refinement and without a storage notification. These storage-failure outcomes apply to audio saved for post-meeting processing; with that processing off, this audio-saving failure and stop message do not apply.

Mac recorded no system audio

Below macOS 13, meeting recording is blocked and changing permissions cannot enable it. The one-time Notetaker blocked dialog says "Recording meetings requires macOS 13 or later"; select Got it to dismiss it. On macOS 13 or later:

  1. Allow System Audio Recording Only on macOS 14.4 or later, or Screen Recording on macOS 13–14.3.

  2. Restart Flow after a fresh Screen Recording grant; System Audio Recording Only needs no restart.

  3. Record again, then open Transcript. If other participants' speech is still missing, report the meeting.

On macOS 14.4 or later, the first permission request can show a prompt in Flow; after a denial, the enable action opens System Settings. On managed Macs with restricted permissions on macOS 13–14.3, it opens Settings without prompting. Both paths open the Screen Recording privacy pane; macOS 13–14.3 has no separate System Audio Recording Only toggle. Restarting to apply the permission, including with Quit & Reopen, rejoins the in-progress meeting except during the guided tour or onboarding.

Windows recorded no other participants' audio

On Windows 10 version 2004 (build 19041) and later, Flow records every output device, so switching speakers or headphones mid-call keeps the other participants' audio. Earlier Windows versions record only your default output device: set the meeting app to play to that device before recording.

If system audio capture stops partway through, Flow restarts it for you and the other participants' audio returns for the rest of the call, lined up with the rest of the recording. If no speakers or headphones are connected, Flow keeps trying until an output device appears or the meeting ends. The System audio capture stopped message appears only when those attempts don't bring audio back — plug in or select an output device and record again.


Transcript errors or missing timestamps

The alert "This sounds like a language we don't support yet" appears only when sustained speech is in a language outside Notetaker's 21 supported languages, and warns that the transcript may contain errors; a brief aside in an unsupported language may not be enough to trigger it, and supported speech never does. Select Learn more to open Use Notetaker with multiple languages in your browser, or Got it to dismiss the alert and keep recording. A different unsupported language triggers its own alert, including later in the same meeting.

In a finished meeting's transcript, the time appears next to the speaker's name on the first turn of each new minute, so a gap between stamps is normal. These are clock times — the time of day the speech was recorded, not elapsed recording time — shown in your region's format, such as "2:28pm" or "14:28". Times aren't shown while a meeting is still recording: stop the recording and reopen the Transcript tab to see them.

For a mistranscribed name or word, or the wrong language, report the meeting under Still stuck?


Speaker names are wrong or missing

  • Unnamed voices while recording: An unnamed voice is labelled by where its audio came from — "You" for your own microphone, "Them" for the other participants' audio, with several unnamed voices on your own microphone numbered "You (Speaker 1)", "You (Speaker 2)". Every unnamed voice in the other participants' audio appears together under "Them", on screen and in copied text, and moves out under its own name as soon as it is named. These labels appear in all supported languages and don't change saved speaker assignments or the refined transcript.

  • Unnamed speakers after the meeting: Participants Flow can't confidently name stay as "Speaker N" so no one is misnamed. In-person one-on-one recordings on a single microphone are usually fully named.

  • Your own speech: When you're the only voice on your microphone — including recordings you paused and resumed, and Microsoft Teams meetings — your lines show as "You" in Transcript even if the meeting app shows a different display name, and your Wispr Flow profile name appears in exports and summaries. Names set on individual lines always win over these labels, and only speakers linked to your own contact are marked "(You)". Flow can't tell you apart when your profile name is only a first name, or when another participant's name is exactly the same as yours.

  • Names in summaries: Anyone who isn't already identified is named only when the transcript is clear, and otherwise described by role. While a meeting with several voices on one microphone is still recording, speakers in the summary aren't resolved until post-meeting processing finishes, and a known name can appear without attribution.

  • Misspelled or misattributed names: Existing transcripts keep the wording they were recorded with. For a misspelled or mistranscribed name, or lines given to the wrong speaker, report the meeting under Still stuck?

Note: If an older meeting still shows "(You)" on the wrong speaker, make any further change to that meeting to bring the labels up to date.

Zoom app on Mac

Names are detected in translated Zoom interfaces as well as in English. When two copies of Zoom are running at once, speaker names are less reliable, so keep a single Zoom instance open.

Microsoft Teams on Mac

Names are read from the Teams interface in English, so set Teams to English. The compact meeting window works, and so does a Teams meeting window parked in the Stage Manager side strip; stretches it can't attribute from the strip are reported as temporarily unavailable rather than as silence. A Teams window on another desktop or Space can't be read.

Teams calls joined in a browser are recognized on teams.microsoft.com, teams.live.com and Teams' newer address, teams.cloud.microsoft. US government Teams addresses aren't supported.

Other participants' speech isn't attributed when the speaker isn't shown on screen at that moment, is waiting in the lobby, or speaks off screen at the same time as someone on screen; a very short remark can also go unattributed. Your own speech is captured through your microphone and named as yours.

Google Meet on Mac (Chrome, Arc, Dia)

In Chrome, Arc and Dia, speaker names continue when you move the call tab to another window of that browser, when the tab is replaced as you join, and when the call is in picture-in-picture while another tab is in front. A call started before the tab finishes loading picks up speaker names shortly after.

A Meet window on another macOS Space, a call tab hidden behind other tabs without picture-in-picture, and compact Meet or Zoom windows in the Stage Manager strip can't be read for names.

In Arc and Dia, speaker names work for Google Meet calls only — not Arc on Windows, and not Teams, Zoom or Slack calls opened in these browsers. Two participants with the same display name are treated as one person, and overlapping speech is attributed to one speaker at a time.

Google Meet on Windows

You can start recording before you join — from Meet's waiting screen, for example — and Flow still picks up speaker names once the call begins, for the rest of the meeting. Flow follows the same call between its Meet tab and the picture-in-picture window, so switching to another browser tab doesn't lose speaker names. Zoom and Slack calls on Windows likewise keep their speaker names if their window closes and reopens during the call.


You can't open or start Notetaker

When a Cloud Sync privacy restriction applies, Notetaker stays visible but starting a recording is blocked before any audio is captured, and the Notetaker blocked message tells you which restriction applies. Notetaker is hidden entirely only when your plan doesn't include it or it isn't available on your platform. An account-specific access decision always overrides your organization's setting, so individual access in an organization without Notetaker gives you the full experience, including the Option+M shortcut and calendar syncing.

  • Just signed in, upgraded or switched accounts: Notetaker appears as soon as the device is signed in and online. Signing out or switching accounts clears the previous account's access and organization and HIPAA details; other restrictions can still apply.

  • Notetaker isn't available for your account: The record button reads this, on Mac and Windows alike, when Notetaker access is turned off for your account — for example your organization disabled it, or your seat doesn't include it. Contact your organization admin or support.

  • Plan or Windows restriction: A full-page message can explain a plan or Windows availability restriction, and the record button names that reason only when it is the actual one. Explicit account access bypasses both.

  • Cloud Sync is required: The blocked message appears in the meeting window, or as a full-page notice if no meeting window is open. It appears once per meeting and can be dismissed; if it can't be shown, you see a short "couldn't start recording" notice instead.

  • Cloud Sync is off: If you turned it off yourself, you can turn it back on. An organization Cloud Sync policy can show a team-settings restriction, but that policy alone does not block recording.

Access changes take effect without restarting Flow: calendar syncing and the Option+M shortcut start working as soon as access is granted, and stop when it's revoked. An organization restriction that blocks recording, or an account that can't be verified, stops the recording straight away and tells you which one it was — resolve that condition rather than retrying. A temporary sign-in or connection problem is retried for you.

Important: Notetaker works alongside a signed personal or organization BAA, so you do not need to revoke your BAA to record meetings. Under a BAA, recording, transcription, summaries, notes and in-app sharing links work, but reporting a meeting to Wispr does not run. If Notetaker still appears blocked, contact support.


Still stuck?

Contact support for missing recordings, repeated processing or save failures, or access that stays blocked. Include your platform, device, meeting title and time, the error, and what you tried. Reporting requires that you're signed in and allowed to upload meeting data.

Note: A report excludes audio but includes your meeting content, such as the transcript, notes and summary, along with diagnostic details about the app. Wispr reviews meeting data to diagnose issues and may use anonymized data to improve products — not for model training unless you chose to share data for model improvement.

  1. Hover the meeting row to reveal ⋯ (More actions).

  2. Select Report, if offered, to open Report This Note.

  3. Select an Issue type; use Missing data or stuck processing for missing recordings or repeated processing.

  4. Enter feedback under What went wrong? — it cannot be blank or only spaces.

  5. Select Send feedback, then Done after "Report sent!" confirms submission.

After "Failed to send report", check your sign-in and upload permission, then resend. Retrying the same unchanged meeting, feedback and Issue type resends the same report rather than filing a duplicate.