Fix "Taking longer than usual" and transcription errors

Mac / Windows

1. Click the Flow icon (menu bar on Mac, system tray on Windows).

2. Select Check for Updates.

iOS

1. Open the App Store and search for Wispr Flow.

2. Tap Update if available.

Android

1. Open the Google Play Store and search for Wispr Flow.

2. Tap Update if available.

Mac

1. Press Cmd + Q to quit Flow.

2. Reopen Flow from your Applications folder or Spotlight.

Windows

1. Right-click the Flow icon in the system tray (bottom-right of the taskbar).

2. Select Quit.

3. Reopen Flow from the Start menu.

iOS

1. Swipe up from the bottom of the screen (or double-click the Home button).

2. Swipe up on Flow to close it.

3. Reopen Flow from your home screen.

Android

1. Open recent apps (swipe up and hold, or tap the square button).

2. Swipe away Flow to close it.

3. Reopen Flow from your home screen or app drawer.

Mac

1. Go to System Settings → Network → Firewall.

2. Confirm Wispr Flow is listed and allowed.

Windows

1. Go to Settings → Privacy & security → Windows Security → Firewall & network protection.

2. Click Allow an app through firewall.

3. Confirm Wispr Flow is listed and allowed.

iOS

1. Go to Settings → General → Background App Refresh.

2. Confirm Wispr Flow is enabled.

Android

1. Go to Settings → Apps → Wispr Flow → Battery.

2. Set battery usage to Unrestricted.

3. Check Settings → Network & internet → Data Saver and confirm Wispr Flow has unrestricted data access.

Mac / Windows

1. Open Flow and go to History.

2. Find the failed transcript (look for Error or Empty status).

3. Click the inline action link: Retry next to the recording duration for Error or Empty status, or Recover at the end of "This transcription was dismissed." for Dismissed or Processing status.

4. Wait for the loading animation to complete. For longer recordings, Flow shows an estimated wait time.

iOS

Retry a failed transcript in one of three ways:

1. Tap a failed transcript to retry it directly. (Tapping a successful transcript copies its text; tapping an empty non-failed transcript does nothing.)

2. Swipe left on a history item to reveal Report, Retry, and Copy. Copy only appears when the transcript has text.

3. Long-press a history item for a context menu with Copy, Retry, Report, and Delete. Copy shows only for successful transcripts with text; Retry and Delete are disabled while a retry is in progress.

Android

1. Open Flow and go to History.

2. Find the failed transcript.

3. Tap Retry transcript from the three-dot menu.

Bugs fixed in recent updates

These issues were fixed in recent versions. Update Flow to resolve them:

• On Windows, Notetaker meeting features (including upcoming-meeting reminders and meeting join controls) could silently show nothing. Restart Flow after updating to catch up pending updates.

• On Windows, a recoverable storage error could wipe local history, transcripts, dictionary, and notes. Flow now clears local data only on genuine corruption and repairs recoverable errors on next launch.

• Valid dictation — including quiet speech or dictated numbers — could be silently dropped, sometimes losing a full minute or more of audio.

• Very short accidental taps (under half a second) could produce fabricated text; they now always resolve cleanly with no output.

• The "Taking longer than usual" notification could appear on successful, fast dictations. It now appears only when processing genuinely takes longer, and dismisses itself as soon as your text is pasted.

• On iOS, network failures during keyboard dictation showed "Audio was silent." The keyboard now shows the correct network-specific error.

• On slow network connections, retrying a dictation could return an empty result.

• When dictating long text into terminal AI assistants, the final portion of text could be missing.

• On Windows, recovery from interrupted shutdown is more reliable — audio is saved alongside transcription, and crashed sessions are detected on next launch.

• On Windows (and occasionally Mac), if the audio system became unavailable after a driver issue, every push-to-talk attempt failed without notice until the app was fully restarted.

• On Mac and Windows, a storage error (such as a full disk or corrupted local data) could cause dictations to fail to save without notice. Flow now shows an actionable notification (see Step 6).

• On Mac and Windows, when the microphone couldn't be accessed at the start of a dictation, Flow could stay in a Listening state before showing a generic "Transcript failed to load" error. It now shows a specific microphone error right away.

• On Mac and Windows, canceling dictation and quickly pressing the hotkey again could make the microphone slow to activate.

• On Android, dictated text could be inserted twice or fail to insert at all.

• Dictated numbers could be deleted or cut off from transcripts.

• Clicking Retry while actively dictating could destroy the in-progress recording. Retry is now disabled during active dictation.

• On Windows, dictation could get stuck on Processing if antivirus or file indexing software had locked a file, or if the disk was full.

• Custom dictionary words were sometimes not recognized if you started dictating immediately on app launch, before dictionary sync completed.

• Background sync and pending app updates no longer interrupt active dictation; update checks still run but don't apply until your current dictation finishes.

• A pending app update could cause Flow to quit mid-dictation.

• In Google Docs and Gmail, dictated text could be inserted multiple times.

• Retrying a long transcription from History could time out too quickly.

• On Android, failed transcriptions did not always preserve the audio recording, making retry impossible.

• On Android, transcription history could be lost when the app was closed.

• Audio recording could be lost when the connection dropped mid-dictation.

• Pressing the Wispr Lens shortcut while a transcription was still processing could start a conflicting session.

What does "Taking longer than usual" mean?

This notification appears on Mac and Windows when Flow needs extra time to process your audio during the Initializing, Stopping, or Processing states, with body text "Your audio is saved for retrying." Common causes are temporary server load, slow internet, or VPN/firewall interference. It dismisses itself once your text is pasted; click Don't show again to hide it permanently.

The notification does not appear during retries and is suppressed in Instruct mode.

What does "Flow was processing your last transcript" mean?

This appears when you start any new dictation, Wispr Lens, or Instruct action — including a retry from History — while a previous transcript is still processing. Wait for it to finish, or press the dismiss shortcut (default Esc) to cancel the in-progress transcription.

Clicking Cancel in the notification dismisses only the notification UI, not the transcription.

What do the microphone error notifications mean on Mac and Windows?

If Flow can't access your microphone when you start dictating, it dismisses the session immediately and shows one of the following:

• No microphone detected: Flow couldn't find a connected microphone. Click Open Sound Settings to check your system's audio input devices.

• Selected microphone is unavailable: The microphone you selected in Flow is no longer connected. Click Choose Microphone to pick a different one.

• Microphone unavailable: Another app may be using the microphone exclusively, or there's an audio driver issue. Click Troubleshoot for next steps.

• Microphone error: An unexpected problem prevented microphone access. Click Troubleshoot for next steps.

• Microphone Permission Required (macOS): Flow doesn't have permission to use your microphone. Click Grant Permission.

• Microphone access is disabled (Windows): Microphone access is disabled in system settings. Click Open Settings.

Microphone unavailable and Microphone error appear only on a repeat failure within a short window, not on the first occurrence. On Windows, Open Sound Settings opens the legacy Sound control panel Recording tab, not the modern Settings app.

What do the error messages mean during iOS onboarding?

When you try dictation for the first time during iOS setup, Flow shows a message at the top of the screen if something goes wrong.

• "Oops, we didn't hear you... Get closer to your mic and try again!": Flow didn't pick up any audio. Move closer to your microphone and try again.

• "Poor connection! Tap the mic to try again": Flow couldn't reach the transcription service. Check your internet and tap the mic to retry.

• "Your mic is being used by another app. Close other apps and try again!": Another app has exclusive access to your microphone. Close other apps and dictate again.

• "Enable microphone access to use Flow": Go to Settings → Privacy → Microphone and enable access for Wispr Flow.

• "Oops, something went wrong... Tap the mic to try again!": An unexpected error occurred. Tap the mic button to try again.

Why are filler words like "um" missing from my transcripts?

Flow's Smart Formatting removes filler words by design. To get raw transcription, turn off Smart Formatting in Settings.

Why do transcripts fail?

• Network timeout: Your internet dropped or was too slow.

• Server processing error: Occasionally the service can't process audio.

• Audio quality issues: Very quiet, distorted, or noisy audio may not process correctly.

• Microphone unavailable: Flow couldn't access your microphone at the start of dictation.

What happens if I lose connection during dictation?

• Before dictating (Mac/Windows): If Flow detects you're offline, it shows a No internet connection notification.

• While dictating: Audio already being recorded may be preserved in History. Check History after reconnecting.

• iOS: Flow tries to transcribe the audio it already captured. Check History after reconnecting.

• Android: Flow does not block dictation when offline. If the connection is lost, the transcription may fail without notice — retry from History.

What's the maximum recording length?

• Mac and Windows: 20-minute maximum. At 19 minutes you'll see a warning that your session is almost up; at 20 minutes the session stops and your transcription is submitted.

• iOS: Recording auto-stops a few minutes after the app is sent to the background. No fixed cap in the foreground.

• Android: No fixed session limit; recording continues until you stop it. For very long content, break it into multiple sessions.

What does the Android Flow Bubble show during errors?

• Failed to transcribe: The bubble shows a Retry button (circular arrow icon) with a toast: "Failed to transcribe. Saved in the app." The failed audio is preserved in History; tapping the Wispr icon starts a fresh dictation.

• Failed to paste (Paste): The bubble shows a Paste (checkmark) button and the text is already on the clipboard. Tapping the Wispr icon dismisses the error.

• Loading spinner and Cancel: A spinner appears during push-to-talk processing, and a Cancel button appears shortly after you release the hotkey.

• Loading states: The bubble shows "Retrying..." while retrying and "Pasting..." during paste retry.

• Offline indicator: When offline, the bubble icon turns grey.

What is Android automatic timeout recovery?

On Android, if Flow appears stuck during initialization or processing, it recovers automatically after a short time so you can dictate again.