-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Common issues and solutions for Vaultend.
Symptoms: Notice shows "AI error [provider] (status): detail"
Solutions:
- Check your API key — go to Settings → Vaultend → AI Provider and verify the key is correct
- Check your balance — ensure your API account has sufficient credits
- Check the model — some models may be deprecated or unavailable. Try a different model from the dropdown.
- Rate limits — if you see rate limit errors, wait a moment and try again. Batch operations may hit rate limits with some providers.
Symptoms: Tag similarity, cross-language tag detection, or link suggestions don't work properly
Solutions:
- Check embedding support — your AI provider must support embeddings. See Settings → Embedding Support.
-
Ollama users — install an embedding model:
ollama pull nomic-embed-text - Custom provider — verify your endpoint supports the embeddings API
- Check the embedding model setting — ensure the specified embedding model exists and is accessible
This notice appears on plugin load if the embedding model can't be reached.
Solutions:
- Check your API key and network connection
- Verify the embedding model name in Settings
- Link suggestions may be temporarily unavailable — core features (tag suggestion) still work
Possible causes:
- Note content is too short for meaningful analysis
- Note content was truncated (notes over 15,000 characters are automatically truncated)
- AI confidence was below threshold (if confidence gating is enabled)
Possible causes:
- No related notes exist in your vault
- Embedding model is not configured (see above)
- Link similarity threshold may be too high — try lowering it in Settings → Link Suggestion
- Large notes take longer to process
- Batch operations (Organize Folder) process notes sequentially and may take several minutes for large folders
- Network latency to your AI provider can affect speed
The plugin caches organize results in memory per session. If you edit a note and organize again:
- Content changed → cache is invalidated automatically, AI runs again
- Content unchanged → cached result is returned
To force a fresh AI call, click Re-organize in the result modal.
Possible causes:
- Notes are in an excluded folder (check Settings → Maintenance → Exclude Folders)
- Notes have an excluded tag (check Settings → Maintenance → Exclude Tags)
- Non-Markdown files (.excalidraw.md, .canvas) are automatically excluded
- Check that Auto Maintenance is enabled in Settings
- Smart scheduling: If no files have changed since the last scan, the scheduled scan is skipped. This is by design to save resources.
- Check the maintenance interval setting
Duplicate detection uses TF-IDF cosine similarity. Very short notes or notes with common vocabulary may produce false positives. You can:
- Dismiss false positives (they won't appear again)
- Use the Open Side by Side button to compare before taking action
Privacy rules are processed in order. Check:
- The rule is enabled (toggle is on)
- The pattern is correct (folder paths are case-sensitive)
- The rule type matches your intent (folder exclude vs tag exclude vs properties exclude)
- Check that the regex pattern is valid
- For simple word masking, just type the word (no regex knowledge needed)
- Redaction only applies to data sent to AI — your original notes are never modified
- Check Obsidian version — minimum 1.7.2 required
- Try disabling and re-enabling the plugin in Settings → Community Plugins
- Check the developer console (
Ctrl/Cmd + Shift + I) for error messages
- Organize Current Note — only appears when a note is open in the editor
- After changing the display language, command palette names update after restarting Obsidian
- The toast undo button is available for 10 seconds after applying changes
- For older actions, use the Activity Log → click Restore
- Some restore operations may fail if the note was modified by other means after the action
If you can't resolve your issue:
- Open the developer console (
Ctrl/Cmd + Shift + I) and check for error messages starting with "Vaultend:" - Create an issue at GitHub Issues
- Include: Obsidian version, Vaultend version, AI provider, and the error message
Vaultend Wiki
Features
Reference