Troubleshooting

Oris is built so that a failure is loud and recoverable rather than quiet and lost. Every path below is documented in full on the page that owns it; this page is the router.

• The summary failed and your note carries a ⚠️ block where it should be. The transcript still landed, and one click re-summarizes it. See when a summary fails.
• The note never arrived. The finished transcript is held safely in Oris rather than lost, and the Recordings tab shows it under Awaiting delivery. See deliveries and receipts.
• The transcript landed somewhere else, in your vault’s inbox/ folder. That happens when the note you recorded into was deleted, or when the spot Oris reserved matched more than one note. See when the note can’t be found.
• A marker is sitting in a note with nothing to replace it, left behind by a run that was interrupted. See recovering markers.
• The other side of the call is missing from the transcript, or a recording refused to start. That is nearly always the lid or the output device. See when the lid is closed and the hardware notes under it.
• Quick notes are landing in Oris rather than in your notes. The quick-notes viewer’s Send to vault is the recovery. See Quick Note.

One failure has nowhere else to live, so it is documented here.

The disk filled up

If a recording keeps failing to write, rather than hiccupping once, and the reason turns out to be that the drive your recordings live on is full, Oris tells you rather than quietly losing audio. You get a single macOS notification reading Disk full — audio write failed. Recording may be losing audio. Free space and stop the recording.

One alert per recording, not a stream of them. Free up some space and stop the recording yourself, at which point the part that was written before the failure transcribes normally. A recording that hit this is still worth stopping properly rather than force-quitting.