Microphone Issues
Microphone Issues
Microphone Not Detected
Make sure your browser has been granted microphone access. If permissions were previously denied, see the Permissions Denied steps below.Verify the microphone is connected
Ensure your microphone is physically plugged in or your device’s built-in mic is not disabled.
Test in browser settings
Go to your browser settings and navigate to Site Permissions > Microphone to confirm access is allowed for Commure Scribe.
Try a different microphone
If you have multiple audio devices, try selecting a different one in the browser’s site settings.
Microphone Permissions Denied
If you’re getting a “Microphone access not granted” error, follow the steps for your browser below.- Chrome
- Edge
- Safari
- iOS Safari
- iOS Chrome
1. If you get a “Microphone access not granted” error, then you may have disabled mic permissions
2. Click on the site setting option next to the address bar
3. Toggle the microphone permission to on (it should be a blue toggle)
4. Make sure to reload the page to apply the change

3. Toggle the microphone permission to on (it should be a blue toggle)

Recording Stuck as 'Paused'
Recording Stuck as 'Paused'
If a paused recording seems to have disappeared, it’s likely still there — just on a different device or app than the one you’re currently checking.
Once a recording is ended and fully uploaded, it becomes available across all devices logged into your account.If you’re switching between the web app and a mobile app, return to the same device and app you used to start the recording to find a paused session.
Stored locally
A paused recording is stored locally on the device and app where it was started — not on Commure’s servers yet.
No cross-device sync
It will only appear on that same device and app until you end the recording and it fully uploads.

Stuck on 'Pending Upload'
Stuck on 'Pending Upload'
If a scribe is stuck on Pending Upload, how you fix it depends on how long it’s been stuck.Recently stuck (same day) — usually recoverable:
Pending uploads are usually caused by a network interruption or the app being backgrounded during upload.Stuck for an extended period (multiple days):If a recording has been pending for an extended period, the local audio file has likely already been cleared by your device’s storage management system. The Upload Again button may error or do nothing, and the recording usually can’t be recovered.To avoid this in the future:

- Make sure you have a stable connection when finishing a recording, and confirm the upload progress bar reaches 100% before closing the app.
- Check your scribes list right after ending a recording to confirm it shows as “In Progress,” not “Pending.”
- Don’t leave a paused or pending recording on your device for more than 24 hours.
Scribe Failed to Generate
Scribe Failed to Generate
If your note didn’t generate, shows an error, or seems stuck on processing, here’s what to check.Common causes:
- A long period of silence at the start or in the middle of the recording
- A phone call coming in during the recording, which interrupts audio capture
- The app being backgrounded during recording (Android) or during upload
-
The microphone not capturing audio

Missing or Lost Scribes
Missing or Lost Scribes
If you can’t find a scribe in your list, it’s often just delayed rather than lost.
Wait and refresh
If there was a connectivity issue during or after the recording, the platform automatically retries the upload several times. Refresh your browser or app once a stable connection is available.
Scroll down
Older scribes load further down the list as you scroll — it may simply be further down than expected.

Note Is Incomplete or Cut Off
Note Is Incomplete or Cut Off
If part of your note is missing or the last section seems incomplete, it’s usually because the note generation hit its processing limit.Why this happens: Notes are generated within a token limit. A few things can push a note past that limit, cutting off the end:
You can review the Transcript tab on the affected scribe to confirm what was actually captured during the visit, even if the note itself is incomplete.To fill in a missing section after the fact, open the scribe, click AI Actions > Add Context, then dictate or type the missing information and click Regenerate. Add Context isn’t available on iOS yet.
- A long or highly detailed template with many sections
- The Citations feature being enabled, which uses additional space in the note
- An unusually long individual encounter

Notes Show the Wrong Date
Notes Show the Wrong Date
If a generated note shows an unexpected date — often defaulting to January 2026 — this is expected behavior, not a bug.Why this happens: The note generation model doesn’t have access to the current date or to the date shown on your My Scribes page — that date is generated separately, by the website interface, and isn’t shared with the model. When no date is mentioned during the recording, the model defaults to the most recent date it’s aware of.How to fix it: State the complete date — day, month, and year — out loud during the recording. The model will use whatever date it hears in the conversation.
Downloading & Exporting Notes
Downloading & Exporting Notes
Commure Scribe doesn’t currently support downloading or exporting notes or recordings as files. Since scribes contain patient information, we’re also unable to send files via email.What you can do instead:
Copying and pasting into your EHR or a document is the recommended workflow for saving notes outside of Commure Scribe.
Copy the note or transcript
Open any scribe, go to the Note or Transcript tab, and copy the text to paste into your EHR or another document.





























