Failed Notes are rare but they do happen occasionally. We understand this is inconvenient and are here to help! 💪
"Unfortunately we could not process a transcript for this session. This session will not be counted towards your usage."
If you've received this error message, read on to learn:
why this error message occurs
how to prevent it in the future
how to generate a new Note for this session
Why does this error message appear?
This error message appears because Blueprint couldn't access your audio. In other words, nothing was recorded so a Note couldn't be generated.
Similar to when you experience issues with other meeting programs (Zoom, FaceTime, etc) like lagging, glitching, or intermittent audio, those things can occasionally happen in Blueprint as well.
💡 The "Duration" field on a failed Note indicates the amount of time the Session window was open, not how long you were actively (or successfully) recording.
So, even if the "Duration" shows 58 minutes, it does not necessarily mean that Blueprint captured 58 minutes of audio.
How to generate a new Note for a failed recording
Though there isn't a way to generate a Note based on the recording (since there wasn't a recording), you can use Blueprint to dictate the session and generate a Note!
When using the Dictation feature, you simply give Blueprint a verbal summary of the session (no need to speak in terms of a progress note) and Blueprint will generate a Note based on your summary.
To dictate a session, head to your Sessions Dashboard and click "Dictate Notes" -- Blueprint will walk you through the rest!
💡 We recommend dictating as soon as possible so that the topics discussed in session are top of mind.
Most common causes and how to avoid them
Blueprint could lose audio access due to a variety of reasons. Here are the most common causes and how to address them:
Blueprint isn't active on your device
If Blueprint isn't active on your device, it won't have access to your audio. The most common things that could push Blueprint to an inactive state on your device are:
Your device has fallen asleep or the screen shut off during recording
Your device received an incoming call or message
Another app is open in front of Blueprint (applies to mobile devices only)
To avoid this:
→ Disable your device from turning off the screen (or set the threshold to a longer period of time than your sessions)
→ Put your device on "Do Not Disturb" mode
→ If you're using Blueprint on a phone or tablet to record an in-person session, make sure Blueprint is the active app showing on your phone or tablet's screen. If another app is showing, that means Blueprint is running in the background and does not have access to your mic.
You're using headphones and the Zoom desktop app to conduct your telehealth session
Because your client's audio is going into your ear (not aloud where your microphone can access it) you must manually share your telehealth audio with Blueprint before beginning your session. However, it's only possible to share audio from another browser tab; it's not possible to share audio from another program such as the Zoom app installed on your computer.
→ If you're using headphones during a Zoom telehealth session, no problem! Just make sure to use the Zoom web client and share that browser tab's audio with Blueprint when prompted before beginning your session.
Your mic is malfunctioning
It's possible that your mic is are disconnecting mid-session, especially if using an external mic such as AirPods
→ If you're using wireless headphones (e.g., AirPods) as your mic, make sure they are charged and remain connected to your device during the recording.
→ Keep an eye on the audio indicator during your session. If you see that Blueprint is no longer detecting audio (a warning message will appear and/or the green indicator won't move) you may need to reconnect your headphones or select a different audio source such as your device's built-in mic.The recording was never started
It's possible that the final "Start Recording" button was never clicked
→ Make sure to start the recording and can see confirmation the "Recording" duration increasing:
💡 The "Duration" field on a failed Note indicates the amount of time the Session window was open, not how long you were actively (or successfully) recording.
So, even if the "Duration" shows 60 minutes, it does not mean that Blueprint captured 60 minutes of audio.
Other causes and best practices
As mentioned above, there are many factors that could be causing audio access issues such as:
a weak wifi signal
your browser's privacy settings blocking Blueprint's access to your mic
using an incompatible internet browser
your computer or phone needing to be restarted
too many tabs or applications open on your device
📚 We recommend checking out this article for more tips: AI Notetaker Troubleshooting Guide