Fix connection and network errors
Last updated: November 20, 2026
Available on: Mac, Windows, iOS, and Android.
If Flow cannot connect, dictation stalls, or text never appears, check the connection before changing app settings. A VPN, proxy, firewall, filtering service, or service interruption can affect Flow even when some websites still load.
Quick checks
Open a website. If other apps are offline too, restore the device's connection first.
Quit and reopen Flow, then dictate a short phrase. If text appears, you're done.
Check the Wispr Flow status page for a reported incident.
Note: On iPhone, sign-in can show “We couldn't reach Wispr Flow. Check your internet connection and try again.” On Mac and Windows, “Connection lost” refers to Notetaker meeting recordings and confirms audio was saved — it is not a dictation error.
Check VPN, proxy, and filtering settings
Important: On a managed device or network, ask IT to make the comparison rather than changing the configuration yourself. A successful test without a tool identifies where to configure access; it does not require leaving protection off.
Test briefly without a VPN or filtering tool only if you control it, then restore it.
Compare the connection with a short dictation after each approved change, then restore the required configuration. If Flow still fails with required protections enabled, continue below.
If a corporate connection is required, ask IT to allow Flow using Configure your network for Wispr Flow rather than leaving it disabled. Allowing website and download domains alone is not sufficient for dictation.
Mac and Windows: proxies and security tools
Flow uses your computer's proxy settings — there is no proxy setting inside Flow. If your organization inspects or filters traffic, ask IT to confirm Flow is allowed.
Quit Flow before changing proxy settings.
Open proxy settings — Mac: System Settings → Network; Windows: Settings → Network & internet → Proxy — and check any active proxy with your administrator.
Add Wispr Flow to a firewall or security tool's allowed-app configuration only if an approved test implicates it, then retest with the tool enabled.
Compare with a DNS server approved for your network if DNS filtering is suspected; DNS filtering can block dictation separately from website access.
Reopen Flow and dictate a short phrase. If text appears with required protections enabled, stop testing.
iPhone and Android
Check the network tools configured on your phone before changing Flow's settings.
iPhone: the active VPN in Settings, any filtering app, and Settings → Wi-Fi → network info → HTTP Proxy.
Android: Settings → Network & internet → VPN, the current network's advanced proxy settings, and any firewall or filtering app; names vary by device.
Chrome extension
If your organization configured the proxy, contact its administrator.
Close and reopen the extension's popup if it shows No Internet Connection.
Check Chrome Settings → System → Open your computer's proxy settings. If the error remains after approved changes, contact support.
Recover after a dropped connection
Important: Saved audio may be retryable; deleted or uncaptured audio is not.
Mac and Windows
“Is your internet connected?” and “Taking longer than usual…” both confirm your audio is saved for retry.
Reconnect to the internet.
Retry the recording from History, or select Retry on the error notification. “Transcript failed to load. You can always recover it from History.” also offers Open History.
Check that the retried text and formatting are complete.
Mac and Windows: Notetaker meeting uploads
When a meeting recording can't finish uploading, the meeting card and the Summary tab explain why, and your recording stays saved.
What you see | What it means |
“Can't reach our servers to upload this meeting…” | A VPN, proxy, firewall, or network filter is blocking the upload. |
“Your connection is too slow to upload this meeting…” | The upload keeps retrying on its own; retry sooner on a faster network. |
“Waiting for a connection” | The device is offline; the upload resumes once you reconnect. |
Turn off the VPN if you control it, or switch to another network.
Select Retry on the notice; it never creates a duplicate meeting. The notice stays until the upload succeeds, so you can retry again later.
iPhone
Flow automatically tries to recover recorded audio when a connection stalls or changes, including switching between Wi-Fi and cellular or turning on Airplane Mode. Recovery can take longer, omit the transcript's ending, or fail; it does not restart cancelled, silent, already failed, or completed dictations. If recovery fails with no text, nothing is inserted and a retryable row is saved in History. Starting a new dictation while an earlier one is still finishing saves the earlier text to History instead of inserting it.
Reconnect, then check History on the device where you dictated.
Tap a failed row without copyable text to retry; its retry option includes the recording length.
Tap saved text in a non-failed row to copy it, then paste it into the intended field.
The Flow keyboard's alert menu does not offer Retry for network or audio-capture errors; you can start a new dictation immediately.
With notification permission granted and the Flow keyboard inactive, a dictation that failed with no text sends one notification — “Your dictation is saved” or one including its length, such as “Your 1:23 dictation is saved” — and Tap to retry opens the app and retries that recording. If a call, Siri, or the time limit ended the dictation, the text is saved instead of inserted, and “Your dictation was interrupted” or “Your dictation reached the time limit” offers Tap to view your transcript, not a retry action.
iPhone: Notetaker meeting uploads
A meeting recorded offline stays saved on your iPhone and uploads by itself once you reconnect. Queued meetings upload one at a time in the background, so you can leave Flow or close and reopen the app.
Reconnect to Wi-Fi or cellular. Waiting meetings start uploading right away.
Retry a meeting that stopped uploading after several automatic attempts; Flow re-sends that specific recording, even if other meetings are waiting ahead of it.
Check the meeting for its notes and summary once the upload completes.
Retries send the same recording, so you never get a duplicate meeting or a second set of notes. A meeting is cleared from the queue only once the upload is confirmed, and time spent offline, a sign-in prompt, or a cancelled upload doesn't use up its automatic attempts.
Android
Flow saves every failed dictation to history, retaining audio when captured: “Failed to transcribe. Saved in the app.” and, during slow processing, “Taking longer than usual. Your audio is saved in the app.” A connection stall alone does not stop dictation while you're speaking; after you stop, Flow automatically attempts to recover stalled dictations.
Reconnect before retrying audio or starting a new dictation. Offline, starting a dictation shows “No internet. Try again later.”
Tap Retry in the error bubble or beside the transcript on Home, not the separate History screen, to transcribe saved audio again; it is unavailable while offline. A successful retry updates the existing history entry without creating a duplicate; if it fails again, Retry is offered again.
Tap Paste to reinsert clipboard text, which works even offline.
Home hides Retry when the entry has no saved recording. “Retry failed. Audio file missing.” or “Retry failed. Audio file not found.” means the audio is unavailable and cannot be transcribed; “Retry failed. Please try again.” means the retry request failed.
If transcription succeeds but insertion fails, Flow switches to Paste with the text on your clipboard. If that fails too, “Failed to paste text. It is still on your clipboard.” means you can paste manually. Tapping the Wispr icon starts a new dictation after a transcription failure, but only dismisses a paste error, preserving clipboard text.
When sign-in fails
Flow explains why a sign-in attempt didn't complete. This applies to Google, Apple, Microsoft, and SSO sign-in, and to connecting apps and services.
Your organization requires SSO: start sign-in again and choose Continue with SSO with your work email.
Your organization requires a different sign-in method, or that method isn't available: use the method your administrator allows.
Extra steps weren't completed: multi-factor authentication, choosing an organization, enrolling a passkey, or a similar check didn't finish — start sign-in again and complete every prompt.
The attempt is invalid or expired: start a fresh sign-in.
Access was denied: contact your administrator.
Too many attempts: wait a short time, then try again.
Temporary outage: wait a few minutes and try again, or check the status page.
If sign-in is interrupted on the provider's page, Flow shows “Sign-in did not finish.” or “This sign-in could not be verified.” Start sign-in again from the beginning. For anything else, Flow says it could not complete sign-in — restart, and contact support if it keeps happening.
Still stuck?
Corporate SSO repeatedly signs you out: ask IT to review the proxy certificate and allowed access.
Flow still cannot connect after these checks: email support@wisprflow.ai. Include your operating system, device, exact error, security and network tools, what you tried, and which comparison changed the result.