Troubleshooting and diagnostics

Troubleshooting and diagnostics

First checks

1. Open Save In options and review any permission or validation banner.
2. Confirm the target path is relative to the default download directory and already exists when a symlink is involved.
3. Check History for the status, mechanism, source URL, selected menu item, and rule metadata.
4. Use Advanced → Diagnostics to inspect or clear the local debug log when debug logging is enabled.

Chrome

1. Open chrome://extensions and enable Developer mode.
2. Find Save In and inspect its service worker.
3. If no worker is shown, trigger a Save In action or reopen options to wake it.
4. Reproduce the problem and copy relevant console errors.

Firefox

1. Open about:debugging#/runtime/this-firefox.
2. Find Save In and choose Inspect.
3. Reproduce the problem while the event-page console is open.

The options page has its own developer console in both browsers; use it for settings, History, Page Sources options, or WebMCP failures.

Reporting an issue

Include:

• Save In version and browser version
• Exact save method (context menu, click-to-save, Page Sources, browser download, or external API)
• Relevant routing rule and destination with private values redacted
• History mechanism/status and useful console errors
• Whether the failure reproduces with fallback fetching disabled

Do not publish authentication URLs, cookies, private paths, full exported settings, or History exports without reviewing them first.