Troubleshooting RecallBase

Symptom

Pick the troubleshooting page that matches what failed: detection, export limits, the PDF dialog, Obsidian app opening, download or clipboard permissions, or Pro unlock.

Most likely cause

Common causes are an unsupported AI page, changed browser permissions, a local daily limit, app-opening behavior, or a subscription status that has not refreshed in the extension.

Fix it

Follow the guide for the failing workflow. Do not send raw conversation text, cookies, tokens, raw DOM, local database files, or sensitive screenshots.

1. 1

   Confirm the AI app is supported.

2. 2

   Refresh the page or extension.

3. 3

   Check account status on your Account page.

4. 4

   Use the related troubleshooting guide.

Verify it worked

Repeat the original action. The extension should show a supported state, the export should complete, or your Account page should show the expected plan.

Start with the smallest reproducible symptom

Troubleshooting is fastest when you isolate one failing action: detection, save, Markdown export, the PDF dialog, Word download, app opening, plan refresh, or a clipboard/download permission. Do not bundle several failures into one report until you know whether they share a cause.

Information that is safe to share

Useful details include browser name and version, extension version, AI app name, export type, whether the page is a real conversation, and the visible RecallBase error message. Never share raw conversation text, cookies, tokens, raw DOM, local database files, or sensitive screenshots.