Find where the pipeline stopped.

No microphone audio

1. Check permission. Settings > Setup must show Microphone granted.
2. Check the input. Select the intended device or System default.
3. Watch the meter. Open Settings > Recording > Levels and speak.
4. Check hardware and virtual routing. Confirm the source is not muted and a virtual device actually carries the microphone.

Meeting Maid has no gain control. A flat meter indicates permission, device selection, mute, or routing rather than post-recording balance.

No audio from other participants

1. Confirm Record the other participants is on in Settings > Recording.
2. Open System Settings > Privacy & Security > Screen & System Audio Recording.
3. Enable Meeting Maid, then restart the app.
4. Play known-safe audio and verify the system meter moves in Settings > Recording > Levels.

Microphone capture continues when system-audio attachment fails. Read the warning instead of assuming both streams stopped.

Automatic recording did not start

• Confirm Start recording automatically when a call begins is on.
• Wait several seconds; the delay prevents stub recordings.
• Confirm Zoom or Microsoft Teams is using the microphone.
• Check Meeting Maid's microphone permission.
• Start manually for other conferencing apps.

Calendar is empty or a match is wrong

• Grant access in System Settings > Privacy & Security > Calendars.
• Add work accounts in System Settings > Internet Accounts when they exist only in Outlook.
• Enable the relevant source under Calendars to Search.
• Remember that the menu bar excludes yesterday's events and hides tomorrow until the local day changes.
• Use Change, Remove match, or Find a match... to correct calendar context. Use Edit Details for the saved title and classification metadata.

Transcription is slow

AWS credentials or access failed

• Use Check credentials in Settings > AWS to isolate profile resolution.
• Confirm the profile exists in ~/.aws/config or ~/.aws/credentials.
• For IAM Identity Center, refresh the session outside Meeting Maid.
• For an assumed role, verify its source profile and role trust.
• For credential_process, run the helper in the same login-shell environment and validate its output independently.
• If credentials resolve, check service-specific IAM actions and regional availability.

A successful credential check does not prove access to Transcribe, S3, Bedrock, or Bedrock Mantle.

Bedrock models are missing

• Confirm the selected profile and region.
• Review model availability and any access requirements in the Amazon Bedrock console.
• Confirm model-listing permissions for standard Bedrock and Bedrock Mantle if used.
• Check whether the zero-retention filter intentionally hides the model.
• Fetch Models again after changing profile, region, or retention filter.

Ollama connection was refused

• Start the server with ollama serve.
• Check installed models with ollama list.
• Confirm the host in Settings > AI Models; the local default is http://localhost:11434.
• For a remote host, check its listener, firewall, and route from this Mac.

Notes or exports are missing

• A transcript must exist before Generate Notes becomes available.
• Test the selected Notes model and inspect any generation error.
• Settings > Export warns when a destination is missing, is not a folder, or is not writable.
• Automatic publishing runs only after notes are generated.
• Select the top-level vault rather than a subfolder to get vault behavior.
• If a name collides with an unrelated file, look for a numbered sibling.
• If the Obsidian CLI cannot open a note, the default Markdown app should open instead; Reveal in Finder remains available.

An interrupted recording did not resume

Meeting Maid retries only when the surviving file is larger than the conservative 4,096-byte header-only ceiling, and it limits retries after repeated processing crashes.

• If a transcript exists, use Generate Notes.
• If only audio exists, choose Share > Export Audio and import the M4A again.
• If neither survived, the meeting displays an explained error rather than retrying indefinitely.

The library was repaired or quarantined

Meeting Maid checks structurally damaged SwiftData stores, attempts repair, and preserves the original before using a replacement. A banner explains whether the library was repaired, quarantined, or opened ephemerally.

Open Settings > General > Storage to inspect the data directory. Do not rename store files or sidecars. Preserve the banner text and log before requesting help.

Collect a useful report

1. Increase logging only if needed. Set Settings > General > Diagnostics to Debug, then reproduce the problem.
2. Open the log. The file is ~/Library/Application Support/MeetingMaid/Logs/meetingmaid.log.
3. Record environment details. Include Meeting Maid version, macOS version, transcription engine, provider, and model.
4. Describe expected and actual behavior. Include exact steps and the latest relevant log lines after reviewing them for sensitive content.

Choose Check for Updates from the Meeting Maid menu before reporting a fixed problem. Update installation is deferred while recording, and Settings > General explains a veto.