Troubleshooting RecallBase

Symptom

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

Most likely cause

Common causes are unsupported AI pages, browser permission changes, local daily limits, app-opening behavior, or a subscription status that has not refreshed in the extension.

Fix it

Use the specific guide for the failing workflow and 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 and confirm the extension shows a supported state, the export path works, or your Account page reflects the expected plan.

Start with the smallest reproducible symptom

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

Information that is safe to share

Useful support 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. Do not share raw conversation text, cookies, tokens, raw DOM, local database files, or sensitive screenshots.