Troubleshooting Guide for 'No Model Available' Error

Last updated: September 8, 2026

Available on: Mac, Windows, iOS, Android

If Flow shows "Flow is having trouble starting," "Something's not right," or stops responding when you dictate, work through the checks and steps below. Most issues resolve in under 2 minutes.


Quick checks

  • Is your internet working? Open any website to confirm. Offline, Flow still starts dictation and saves your audio so you can retry it from History once you reconnect.

  • Is Flow up to date? Flow checks for updates automatically and applies them in the background when you're not dictating.

  • Did you just plug in a new mic? Declining the Switch prompt on the "{Device} detected" notification leaves your old mic selected, which can cause 'no audio' errors.

  • Does restarting Flow fix it? Quit Flow, reopen it, and dictate a short phrase. If text appears, you're done.

  • Does your mic work in other apps? Record a short clip in Voice Memos (Mac/iOS) or Sound Recorder (Windows/Android). If it's silent there too, the problem is system-level — not Flow.


Common error messages

Note: Error messages name the microphone in use (for example, "We didn't pick up any audio from MacBook Pro Microphone") so you can identify which mic was active.

"Flow is having trouble loading" or "Flow is having trouble starting"

Flow failed to initialize; "Flow is having trouble starting" appears after several failed retries. Click Restart Flow in the notification, or Contact us to reach support.

"Audio system failed to load"

Flow's audio system couldn't initialize. Click Restart Flow in the notification, or Contact us if it persists.

"Something's not right"

Transcription failed. Most interrupted dictations recover automatically; if yours didn't, click Retry or Open History to recover the transcript.

"Is your internet connected?"

Your internet connection may be unavailable. Open any website to verify. Dictation still starts and your audio is saved; if transcription fails, use Retry or Open History once you're back online.

"Couldn't start audio capture" (iOS keyboard)

The Flow keyboard couldn't begin recording — you switched away from the keyboard right after opening Flow, another app (such as a phone call) is holding the microphone, or Flow wasn't ready after a cold launch. Tap Retry, or Dismiss to close the message. If it keeps returning, quit and reopen the Flow app.

"Is your microphone muted?" or "We couldn't hear you"

Flow isn't detecting audio from your selected microphone. Check for a hardware mute key on your keyboard or headset, then click Select microphone to try a different mic, or Troubleshoot for help.

"No audio received" or "Microphone is not working"

"No audio received" appears first when Flow doesn't hear anything, with a Contact us button. If silence continues, it escalates to "Microphone is not working," which offers Select microphone and Contact us.

"No microphone detected"

Flow can't find a microphone on your device. Connect a microphone and try again.

"Selected microphone is unavailable" or "Microphone unavailable"

"Selected microphone is unavailable" — your previously selected microphone can't be accessed. Close other apps that use audio, then click Choose Microphone and select a different one.

"Microphone unavailable" — another app may be holding the mic, or the audio driver may be stuck. Close other apps that use your mic and try again, or click Troubleshoot.

"Microphone error" or "Unable to access mic"

Flow hit a problem with your microphone. Check permissions, confirm no other app is holding the mic, and try selecting a different mic or reconnecting your current one.

"Microphone disconnected"

Your microphone disconnected during dictation. Click Insert to paste the audio captured up to that point.

"Your laptop lid is closed" (Mac only)

The built-in mic is unavailable when the lid is closed. Click Select microphone to choose an external mic.

"Microphone Permission Required"

Flow needs microphone access. Click Grant Permission:

  • Mac: Triggers a system permission prompt on first use; if you previously denied access, it opens System Settings → Privacy & Security → Microphone.

  • Windows: Opens your system microphone privacy settings. A separate "Microphone access is disabled" notification means system-level microphone privacy is off and needs to be enabled.

"Accessibility Permission Required"

Flow needs accessibility access. Click Open Settings to grant permission.

"Transcription session ended"

Dictation length is capped per session: 5 minutes on Android and iOS, roughly 6 minutes on desktop. On Android, a toast warns "1 minute left before you reach the 5-minute limit." then "Session ended, 5-minute limit reached"; in the background, a notification titled "Session ended" reads "Flow supports up to 5 minutes per session."

Admin policy or IP allowlist block (managed devices)

On managed devices, an admin policy can block a dictation outright — this is not a permissions or mic issue. On iOS, an organization IP allowlist can block sign-in with a full-screen message offering Retry and Sign Out.

Failed dictations in Hub → Home history (Mac and Windows)

A failed dictation appears in your Hub → Home history in one of these states:

  • Transcript interrupted — an error stopped the transcription.

  • No microphone detected — no mic was found at the time of dictation.

  • Silent audio — no speech was captured.

  • Dismissed or processing — offers a Recover link.

Report any history row via the flag icon.


Troubleshooting steps

Follow the steps for your platform in order. After each step, dictate a short phrase — if text appears, you're done.

Mac

  1. Check System Settings → Privacy & Security → Microphone: Wispr Flow must be listed with its toggle on. If Flow shows "Microphone Permission Required," click Grant Permission.

  2. Check System Settings → Privacy & Security → Accessibility: Wispr Flow must be listed with its toggle on.

  3. Select a different microphone: click the Wispr Flow icon in the menu bar → Microphone → choose another mic. With the laptop lid closed, use an external microphone.

Tip: If you're using AirPods, switch to the built-in mic or another external mic. AirPods can be slow to connect and may cause errors during dictation.

  1. Restart your Mac from the Apple menu → Restart, then open Flow and dictate.

  2. Reset Flow data: open Flow → Settings → System → Data → Reset app, then click Reset & restart.

Warning: Use the reset step only if directed by Wispr Flow support. It deletes Flow's local data (transcription history, cached data). Your dictionary, stats, settings, notes, and meetings are preserved and re-sync from the cloud after Flow restarts.

Windows

  1. Open Settings → Privacy & security → Microphone and turn on both the global "Microphone access" toggle and "Let apps access your microphone." If dictation fails, Flow opens this page for you.

  2. Select a different microphone: click the Wispr Flow icon in the system tray → Microphone → choose another mic.

  3. Restart your computer from Start → Power → Restart, then open Flow and dictate.

iOS

  1. Enable Full Access for the Flow keyboard: Settings → General → Keyboard → Keyboards → Flow → turn on Allow Full Access.

  2. Grant microphone access: if it's denied, tap Go to Settings on the mic-access card on the Wispr Flow home screen. Home-screen setup cards stay hidden until microphone access is granted.

  3. Retry after "Couldn't start audio capture," then tap the mic icon to start a new dictation.

  4. Force close Flow: swipe up from the bottom of the screen, swipe the Flow app away, then reopen it and dictate.

  5. Turn on Low Data Mode for slow connections: Wispr Flow app → Settings → General → Low Data Mode (in the Wispr Flow app, not iOS System Settings).

Note: Without Full Access, tapping the keyboard opens a setup modal; Finish Setup shows a two-step privacy guide before Settings. Flow re-checks microphone access and keyboard Full Access when you return from Settings — no relaunch needed.

Note: When a dictation is saved but not pasted, iOS posts a local notification: "Your dictation was interrupted" / "Tap to view your transcript", "Your 1:23 dictation is saved" / "Tap to retry" (tapping auto-retries that transcript), or "Your dictation reached the time limit" / "Tap to view your transcript". These appear only if notification permission is already granted.

Android

  1. Open Settings → Apps → Wispr Flow → Permissions and confirm Microphone, Overlay, and Accessibility are granted.

  2. Force stop Flow: Settings → Apps → Wispr Flow → Force stop, then reopen Flow and dictate.

  3. Restart your phone: hold the power button, tap Restart, then open Flow and dictate.

Note: Follow the prompts on any home-screen card that appears, including Battery Optimization ("Keep Wispr Flow running") and service state ("Flow Bubble Disabled"). Android also posts a system notification when accessibility permission is lost or the service needs a restart; with notifications disabled, this appears as an on-screen toast.

Note: If transcription fails, Flow shows "Failed to transcribe. Saved in the app." with a Retry button on the Flow Bubble; the recording can also be retried from the home screen, but only while the original recording file still exists. If pasting fails, the text stays on your clipboard and the Flow Bubble shows a Paste button.

Note: If the Flow Bubble is missing rather than erroring, check the home screen for a "Bubble is snoozed" card — tap End snooze now, or shake your phone while inside a text box. The bubble does not appear until you finish onboarding, even if permissions are granted.

Note: Hitting the weekly word limit can look like a failure. Android shows 'No words remaining' with "Flow will slow down until next week" (soft cap) or "You've hit your weekly word limit. Upgrade to continue using Flow." (hard cap) and a Get unlimited words button. On iOS, hitting the 1,000-word weekly limit may grant 5,000 bonus words.

Note: Notetaker is not available on Android, so reproduce Notetaker-related dictation issues on Mac.


FAQs

Will I lose my transcriptions if Flow crashes or the connection drops?

Usually not. On Mac and Windows, an interrupted dictation is normally recovered and transcribed; short and normal dictations are unaffected. Recovery limits:

  • Very long recordings: May show a transcription error; use Retry or Open History to recover manually.

  • If recovery takes too long: Whatever was transcribed is pasted, so text may be truncated rather than lost.

  • Dismissing or starting a new dictation: Stops recovery of the old one, and nothing is pasted from it.

  • Desktop manual retry: Available for failed or empty transcripts, but not while a dictation is in progress.

  • History disabled: If local history storage is off by your own setting or an enterprise policy, the History page shows a "history disabled" message and failed transcripts cannot be recovered.

Why does the error keep coming back after restarting?

Recurring errors usually point to a permissions issue or a mic that isn't working. Work through the full troubleshooting steps for your platform.

Why does dictation sometimes stop working silently?

Some mic errors only appear after repeat failures, to avoid interrupting you. If dictation stops without an error, check your microphone in your system's Sound Settings and try again. After an error, start a new dictation immediately — no restart or reset needed. Flow ignores the shortcut only while it is initializing, stopping, processing, or retrying.


Still need help?

If dictation still fails, reach out to support. Most issues are resolved in one reply.

  • Mac/Windows: Click Help in the sidebar → Talk to support, then select the Report an issue tab.

  • iOS: Go to Menu → Talk to Support.

  • Android: Open the drawer → Report an issue, select a request type (Issue, Billing, or Account management), write your message, and tap Send. If you're offline, your draft is kept.

  • Include: your platform, device, the error you're seeing, and the steps you've tried. A screenshot helps (PNG, JPEG, BMP, or WEBP, max 10MB, one file per submission).

Note: On Mac and Windows, if the submission fails, your message is copied to your clipboard so you can try again.