Fix an output that couldn't be generated
If you've received a notification that your Filenote AI output couldn't be generated, it's usually for one of the reasons below. Find your situation in the table, then follow the steps in the "What to do" column to get things moving again.
| Reason / error message | What this means | What to do |
|---|---|---|
| The meeting wasn't recorded | Filenote AI needs a recording to create a file note. Without one, there's nothing for it to work from. |
|
| The recording had no audio (e.g. it was on mute) | Filenote AI couldn't detect any audio in the recording, so it couldn't create a file note. This usually means the recording was muted, the microphone wasn't on, or the audio was captured at a very low volume. |
For future meetings, check your microphone and mute settings before the recording starts. |
| The meeting was transcribed rather than recorded in Microsoft Teams | A file came through, but it didn't contain any audio. This usually happens when a meeting is transcribed rather than recorded in Teams, so there's no sound to build the file note from. A transcript may still be available, even though the recording has no audio. |
|
One or more generated outputs need manual review before delivery | Filenote AI finalised some of your outputs, but couldn't finalise the others automatically. Those outputs are waiting in Tasks for you to review and finalise. Your email shows which outputs were finalised (and where they were delivered), and which ones still need finalising. |
|
Still stuck?
If none of the above matches what you're seeing, or you've tried the steps and it's still not working, forward your output email to support@blvsolutions.com and we'll take a look for you.
| Need help? If you run into any issues or have questions, our support team is here to help. Email Support → |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article