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 a retry 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 section shows it under Awaiting delivery. See deliveries and receipts.
• Your Markdown folder moved, was renamed or was deleted. The Save to row in General → Destination, and the Check destination line under the record button, both say “Oris can’t find your folder. Choose it again with “Choose folder…” in General.” Move the folder back, or choose it where it is now with Choose folder…. A meeting that finished while the folder was missing waits under Recordings → Awaiting delivery, where its row says the same sentence, and you deliver it from there once Oris can see the folder again. See changing your destination.
• Your Markdown folder became read-only. The destination check only asks whether the folder is there, so it stays green, and Oris finds out when it tries to write the note. That meeting waits under Awaiting delivery rather than being lost. Make the folder writable again and retry it from there. Retry always tries the folder the note was headed for, so if you choose another folder instead, use Send here instead… on the waiting meeting. Choosing a folder Oris can’t write into is refused on the spot with “Oris can’t write into that folder”, and your destination stays as it was.
• The note you append to was deleted. With Append to one note, Oris doesn’t recreate the note on its own, because you may have removed it on purpose, so each meeting waits under Awaiting delivery instead. Choose the folder again with Choose folder… and Oris makes the note again, with its name as the heading, or put a file with that name back yourself. Then retry what was waiting. See how a folder destination lands notes.
• Apple Notes access was turned off. Meetings on their way to Apple Notes wait rather than fail. The waiting recording reads Waiting for Apple Notes access, and Awaiting delivery says “Apple Notes access is turned off”, with an Open Apple Notes access button that takes you to the row in General, and General’s Destination check and the record button’s Check destination say the same with the way to fix it: “Apple Notes access is turned off. Turn it on from “Apple Notes access” in General.” Turn Notes back on for Oris under System Settings → Privacy & Security → Automation, quit and reopen Oris from the menu bar icon if macOS didn’t, and everything that was waiting delivers itself. See the permission macOS asks for.
• An Apple Notes note is waiting because Oris was quit. Only the Oris app can write into Notes, so a meeting recorded from the Obsidian plugin while Oris was quit is saved and waits for it. The notification reads Transcript saved, “Open Oris to finish delivery to Apple Notes.” Click it, or open Oris any other way, and the note is delivered within moments. See deliveries go through the Oris app.
• 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. That is nearly always the output device. See when the lid is closed and the hardware notes under it.
• A recording refused to start. The reason appears under the record button. If it says microphone access is off, see permissions.
• Quick notes are landing in Oris rather than in your notes. The quick-notes viewer’s send control — Send to vault, Send to folder, or Send to Notes, named for your destination — 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.