“Flow hit a snag” before setup finishes
Last updated: November 6, 2026
Available on: Mac, Windows
You may see “Flow hit a snag” after loading, while your dictation shortcut does nothing. If Flow gets stuck after sign-in on Windows or Mac, a different network may help you finish setup.
What's happening
If startup loading remains stuck for about 20 seconds after sign-in, Flow shows “Flow hit a snag”. The error can recur on each launch while the blocking condition persists. If loading briefly clears and then stalls again, the 20-second wait starts over.
Flow can take too long to load your account details during first-time setup. This is more likely on slow, restricted or company-managed networks, such as a corporate VPN or proxy.
Startup can also be held up while Flow confirms your sign-in, loads team details, prepares setup steps or checks microphone access on Windows. Waiting on the signed-out login screen or an approved-network block does not trigger this stuck-loading error.
Outside the “Try It Yourself” practice pages, the dictation shortcut does nothing and shows no notification until setup finishes.
This is an issue on our side, not something you did wrong. Our team is working on a fix.
Try these recovery steps
1. Restart Flow
Note: The error screen says: “Your data is safe and we’re looking into the issue. Try again, or restart Flow if the issue persists.”
Saved organization details are kept after network errors or timeouts; they are cleared only when Flow confirms your account has no organization.
A slow account-details load can recover while you wait. Restarting does not require a network change.
Click Restart Flow on the error screen.
Complete any remaining setup steps when Flow reopens.
If setup finishes and you can dictate, you're done. If the error returns, try the permitted-network option below.
2. Try a different permitted network
Important: If you're unsure, check with your IT team first. If your organization only allows Wispr on approved networks, signing in from another network is itself blocked, and you'll see a separate “Your network isn't allowed” screen instead.
Try completing setup once on a different network:
If your company allows it, disconnect from your company VPN or proxy, or switch to another Wi-Fi network or a phone hotspot.
Open Flow again and try completing setup.
If setup finishes, test dictation. If the error returns, contact support. This workaround doesn't work for everyone: changing networks does not resolve every account-access, sign-in or service error.
If you see “Your network isn't allowed”
This block signs you out. Retrying on a blocked network returns you to the same screen.
Switch to a network your organization approves.
Click Retry.
Complete sign-in again.
If the block clears, continue setup. If it returns or you cannot use an approved network, contact your admin.
Choose Sign Out to leave the blocked sign-in flow instead.
FAQs
Can this happen after setup finishes?
Finishing setup removes one of the ways this screen can appear, but it can still show up later — for example if Flow can't confirm your sign-in state at launch, or if your organization asks you to select a team again. The same screen can also appear if the Flow window crashes, so it is not exclusive to setup.
What if Flow says it cannot load team data?
During account loading, Flow may also show “This is taking longer than expected” or “Unable to load team data. Please try restarting the app or contact support.” Use the recovery steps above for these messages.
Still need help?
The Contact support button opens an email to support@wisprflow.ai with the subject “Flow Desktop Error” and an empty message body.
Contact support and mention that you're seeing “Flow hit a snag” before setup. Include your app version and, if you're using a work account, your company name.
Also add your platform, device, account email and the steps you tried. The screen does not display the underlying technical error message.
Error reports for signed-in users include their account ID, email and name.