Troubleshooting audio playback & AirPod issues (iOS, macOS)

Last updated: November 17, 2026

Available on: Mac, Windows, iOS

If AirPods switch devices, playback stays muted or paused, or dictation cuts out, check your input and playback settings, then use the recovery steps for your platform.


Quick checks

  • Using AirPods? Built-in or wired microphones are recommended for dictation. The desktop picker warns: "AirPods may be slow to start and have more errors in dictation. We recommend the built in microphone."

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


Choose and test a microphone (Mac/Windows)

Warning: Finish dictation before opening the microphone picker. Opening it mid-dictation interrupts transcription. Flow attempts to save captured audio to History, but saving can fail; no audio is saved if none was captured or your organization prevents audio storage.

  1. Open Flow → Settings → General.

  2. Click Change beside Microphone.

  3. Select Built-in mic (recommended) or another input. Auto-detect follows your computer's default input; Windows may not recognize every Bluetooth headset as Bluetooth, so select the device directly when needed.

  4. Speak into the mic and check that the level meter responds. A flat meter means no usable sound, including input too faint to hear; changing inputs restarts the test.

  5. Press Esc to close the dialog and stop the mic test.

  6. Dictate a test phrase; if text appears, the input is working.

This choice affects dictation only. Dictation shortcuts do nothing while the test is open, and a silent test produces no no-audio notices.

Recover a dictation interrupted by the mic test

Recovery requires saved audio and a History item less than 14 days old. For empty or failed recordings, retry also requires at least five seconds of audio.

  1. Close the mic test before retrying; retries are blocked during active dictation or testing.

  2. Open History.

  3. Select Recover on the interrupted recording, when available.

If stored audio is unavailable, Flow shows an error instead of recovering text.

When microphones connect or change

Flow prefers the highest-ranked connected mic. Connecting a higher-ranked mic does not interrupt dictation; Flow uses it for the next recording.

For a newly connected, unranked physical mic other than AirPods, "<device name> detected" offers Switch and Don't Switch without automatically switching. It does not appear during mic testing and waits until dictation ends if you connect the mic while recording. Virtual inputs stay selectable under Show other devices (N), but are never ranked, chosen or prompted automatically.

With AirPods selected after setup, "AirPods aren't the best for dictation" can appear at dictation start at most once per hour without blocking recording. Switch microphone opens the picker; Don't show again permanently dismisses the tip, as does muting its notification category.


Playback and AirPods switching on Mac

Setting

Effect

Mute all audio while dictating — System

Mutes other audio during dictation.

Pause music while dictating — Experimental

Pauses music instead of muting all audio.

Dictation and notification sounds

Turn this on to hear dictation cues.

Enabling either mute or pause disables the other. With a Bluetooth headset, playback can remain muted or paused for several seconds after dictation while the headset returns to its normal audio mode; Flow restores playback even if it does not settle. A mute already present before dictation is left unchanged.

Missing start or stop sounds

With sounds enabled, the Mac start cue normally coincides with recording, but plays early for Bluetooth audio-mode changes. AirPods returning from music mode can lose the first cue without affecting recording.

The stop cue is skipped if the headset changed audio modes during dictation or recording ended before the start cue played. Flow clears a system mute caused by the Bluetooth switch only when it can attribute the mute to that switch.

Stop AirPods from auto-switching (Mac)

AirPods jumping from iPhone to Mac is Apple's automatic device switching, not Flow.

  1. Open Apple menu → System Settings → Bluetooth.

  2. Click the i next to your AirPods.

  3. Set "Connect to This Mac" to When Last Connected to This Mac.

  4. Move AirPods back to your iPhone manually if they jump to your Mac.

Dictate a test phrase. If AirPods stay on your intended device, this step worked.


Recover from desktop audio errors

Select microphone and Choose Microphone open the picker. Troubleshoot opens microphone troubleshooting in your browser; use that guide for missing devices, blocked access, or microphone-start errors.

Notification

What to do

Microphone disconnected

Recording stopped; select Insert to paste text recorded before disconnection.

Is your microphone muted?

No audio was captured; select Select microphone or Troubleshoot.

We couldn't hear you

No speech was picked up; select Select microphone or Troubleshoot.

Unable to access mic

Select Restart App if microphone access remains stuck.

The muted-mic notice appears after a dictation captures no audio, and Unable to access mic can appear after eight seconds waiting for access, clearing automatically if access succeeds.

Faint input can count as silence. An entirely silent recording produces no transcript; a faint stretch after speech does not prevent normal transcription. For silence from the start, finish recording and check the result rather than relying on an in-dictation warning.

After each recovery action, dictate a test phrase and confirm text appears. A missing repeat notice does not confirm recovery.


Recover from audio interruptions (iOS)

  1. Open Flow Settings.

  2. Enable Use your device mic to use the built-in microphone instead of Bluetooth input.

  3. Dictate a test phrase and confirm text appears.

Starting a dictation or meeting recording stops History playback or in-app video, including Picture in Picture, until the microphone is released, and playback won't start while a dictation or meeting holds the microphone. History playback also stops when Flow leaves the foreground or you retry or delete a recording.

Recording stops during a call or device change

An incoming call stops dictation. After a call or Siri interruption, recording can resume automatically if the interruption ends within your background-recording time limit, or whenever that setting is 0. If it does not resume, tap the keyboard's mic button to start again.

Connecting or disconnecting an audio device stops active dictation; an audio-output override does not stop dictation when the built-in mic remains selected.

A Notetaker meeting recording keeps running through a Bluetooth connect, disconnect or other audio-device change: Flow moves the recording to the new microphone and live transcription continues, losing only a fraction of a second of audio. It also keeps capturing and saving if the app is briefly busy or you switch apps.

If a phone call interrupts a meeting recording, Flow pauses it and makes one attempt to resume the same meeting when the call ends. If it can't resume — or after a Siri interruption or audio failure — the meeting is completed and the captured audio is saved and processed. While the interruption is active, Record and Resume are unavailable and Flow explains that the microphone is in use.

If a call, Siri, or the five-minute limit ends dictation while the keyboard is inactive, the transcript is saved to History and a notification opens that recording. Command-mode queries are excluded, and stopping dictation yourself does not trigger the duration-limit notification.

A meeting is still processing or shows Upload failed

When you reopen Flow, a meeting recording that hasn't been sent yet uploads on its own if its last saved audio is no more than five minutes old. Home and the meeting's detail screen show Processing while that finishes.

Otherwise the meeting shows Upload failed with a Retry action — tap Retry on the meeting, or tap the saved-recording notification, which retries the upload and opens the meeting. A recording you paused yourself stays paused and can be resumed after reopening the app.

Music appears in your meeting transcript

Music from other apps keeps playing while a Notetaker recording runs, and audio played through the phone speaker can be picked up by the microphone and show up in the transcript. Pause the music or use headphones while recording. With Bluetooth headphones, music plays at call quality during a recording.

Recording errors and microphone conflicts

Recording errors identify audio, transcription, network, mic-in-use, or permission problems, or say "Unknown error. Please try again." Network failures stop dictation; check your connection before retrying. For Microphone access denied, use Go to Settings and turn on Microphone.

If a meeting recording can't start because something else is using the microphone, Flow shows "The microphone is unavailable. Try again." Close whatever else is using the mic, then start the recording again. Dictation and Notetaker can't use the microphone at the same time, so stop one before starting the other; the recording already in progress keeps going.

A failed dictation is still saved: Retry starts dictation again, and when the keyboard isn't visible a notification lets you tap to retry. If audio cannot start, the full-screen audio-failure view offers Retry and clears automatically when recording starts.

After retrying, dictate a test phrase and confirm text appears.


Still stuck?

Contact support if recording still fails after selecting an input, granting access, or reconnecting the mic. Mac: Help → Talk to support. Windows: Talk to support in Flow's system tray menu or the app sidebar's Help menu. iOS: Menu → Talk to Support.

  1. Select Report an issue, not Share feedback.

  2. Choose Issue as the request type; desktop pre-selects it, and iOS has no selection.

  3. Describe the problem, your platform, device model, and steps you've tried.

  4. Send your request; a request type and description are required.

Note: Support requests include app logs and request details. iOS also includes app and OS versions, device name/model, and timezone.

If sending fails on desktop, Flow reports the error and copies your message to the clipboard so you can paste it and retry. On iOS, a failed send shows an error without copying the message.