Troubleshooting

Troubleshooting & Error Guides

This page contains guides for troubleshooting common issues and using diagnostic tools.

---

🚀 Jump to Rem by ID - User Guide

📖 Overview

The "Jump to Rem by ID" feature allows you to quickly navigate to any rem in your knowledge base using its RemId. This is especially useful when investigating errors from the pre-computation process or debugging issues with specific rems.

⚡ Quick Start

Using the Plugin Command (Recommended)

1. Press Ctrl+/ (or Cmd+/ on Mac)
2. Type: Jump to Rem by ID
3. Enter the RemId in the popup dialog
4. Press Enter or click "Jump to Rem"
5. Done! The rem opens automatically

Example:

Ctrl+P → "Jump to Rem" → tfhQYD3Q2wDw4VWUH → Enter → ✅

🎯 Common Use Cases

1. Investigating Pre-computation Errors

When you run "Pre-compute Card Priorities" and see errors:

Step 1: Check the console for error details

Error 15/268:
  RemId: tfhQYD3Q2wDw4VWUH  ← Copy this
  Reason: Processing exception

Step 2: Jump to the rem

• Ctrl+/ → "Jump to Rem by ID"
• Paste: tfhQYD3Q2wDw4VWUH
• Press Enter

Step 3: Investigate

• View the rem's content
• Check if it's corrupted
• Fix any issues
• Re-run pre-computation

2. Checking Multiple Failed Rems

When you have a list of failed RemIds:

=== FAILED REM IDs ===
abc123xyz
def456uvw
ghi789rst

Quick workflow:

1. Ctrl+/ → "Jump to Rem by ID"
2. Paste first RemId → Enter
3. Investigate the rem
4. Repeat for next RemId (command stays in recent commands)

Pro tip: The command stays in your command history, so just press Ctrl+P and it will be at the top of your recent commands!

3. Verifying Orphaned Cards

When you see "Rem not found" errors:

Use Jump to Rem to confirm:

• If popup shows "Rem not found" → The rem was deleted (orphaned)
• If rem opens → The rem exists (error was temporary)

🎨 The Popup Dialog

When you run the command, a popup appears with:

┌─────────────────────────────────────┐
│  Jump to Rem by ID                  │
│                                     │
│  Enter RemId:                       │
│  ┌─────────────────────────────┐   │
│  │ e.g., tfhQYD3Q2wDw4VWUH    │   │
│  └─────────────────────────────┘   │
│                                     │
│          [Cancel]  [Jump to Rem]   │
│                                     │
│  💡 Tip: Find RemIds in the         │
│     pre-computation error log       │
└─────────────────────────────────────┘

Features:

• ✅ Auto-focused input - Start typing immediately
• ✅ Enter key support - Press Enter to submit
• ✅ Error messages - Clear feedback if RemId is invalid
• ✅ Cancel button - Close without action
• ✅ Dark mode - Adapts to your theme

🔍 Understanding RemIds

What is a RemId?

A RemId is a unique identifier for every rem in RemNote. It looks like this:

tfhQYD3Q2wDw4VWUH

Where to Find RemIds:

1. Pre-computation error logs (Console, F12)

   Error 15/268:
     RemId: tfhQYD3Q2wDw4VWUH
   

2. URL bar when viewing a rem

   https://www.remnote.com/document/tfhQYD3Q2wDw4VWUH
   

3. Developer tools (for debugging)

   const rem = await plugin.focus.getFocusedRem();
   console.log(rem._id); // Prints RemId

✅ Success Messages

When rem is found:

🔍 Searching for rem: tfhQYD3Q2wDw4VWUH...
✅ Found rem: "What is the capital of France?"
📍 Opening rem in RemNote...

Result:

• Popup closes automatically
• Rem opens in RemNote
• Toast notification: "✅ Found: What is the capital..."

When rem is not found:

🔍 Searching for rem: tfhQYD3Q2wDw4VWUH...
❌ Rem not found: tfhQYD3Q2wDw4VWUH
💡 Possible reasons:
   • The rem was deleted
   • The RemId is incorrect
   • The rem is from a different knowledge base

Result:

• Error message shown in popup: "Rem not found: tfhQYD3Q2wDw4VWUH"
• Popup stays open so you can try again
• Toast notification: "❌ Rem not found"

🚨 Error Messages & Solutions

Error: "RemId cannot be empty"

Cause: You clicked "Jump to Rem" without entering anything

Solution: Enter a RemId in the input field

---

Error: "Rem not found: [RemId]"

Cause: The rem with this ID doesn't exist in your knowledge base

Possible reasons:

1. The rem was deleted
2. You copied the RemId incorrectly
3. The rem is in a different knowledge base
4. Typo in the RemId

Solutions:

• Double-check you copied the full RemId
• Verify you're in the correct knowledge base
• Check if the rem was recently deleted
• Try another RemId from your error list

---

Error: "Error: [technical message]"

Cause: Unexpected error during processing

Solutions:

1. Try again (might be temporary)
2. Reload the plugin (Settings → Plugins → Toggle off/on)
3. Check console for detailed error (F12)
4. Report bug if error persists

---

🛠 Pre-compute Card Priorities - Error Guide

Understanding the Error Report

When you run the pre-computation, you'll now see an enhanced error report like this:

✅ Pre-computation complete!

• Total rems processed: 41010
• Newly tagged: 40948
• Preserved manual priorities: 62
• Errors: 268
• Error breakdown:
  - Rem not found: 245
  - Processing exceptions: 23
• Total time: 443s
• Cache build time: 142s

Check console for detailed error log.

Future startups will be much faster!

Error Types Explained

1. "Rem not found" Errors

What it means: The card references a Rem that no longer exists in your knowledge base.

Why this happens:

• The Rem was deleted but the card still exists
• Database inconsistency
• The card's parent Rem was removed

Impact:

• ❌ The card was NOT tagged with cardPriority
• ❌ No priority was assigned
• The card may not appear correctly in the queue

How to fix:

The plugin now handles this automatically! When you run "Update all inherited Card Priorities", if any "Rem not found" errors are found, it will immediately offer to clean them up:

1. A summary confirms how many orphan cards were found and across how many missing Rems.
2. The full list is shown in pages of 25 (so the dialog always fits on screen).
3. Each page asks for your confirmation before proceeding — you can cancel at any point.
4. Confirmed orphan cards are removed in parallel batches of 25 with live progress toasts.

Each candidate is double-checked with a fresh live lookup before removal, so cards belonging to Rems that were only transiently unavailable are never deleted.

Tip

If you prefer to investigate manually first, you can cancel the cleanup dialog and use the "Jump to Rem by ID" command (Ctrl+/) to inspect individual RemIds from the console log.

2. "Processing exceptions" Errors

What it means: An unexpected error occurred while processing the Rem.

Common causes:

• Permission issues
• Corrupted Rem data
• Network timeout during processing
• Bug in the code logic

Impact:

• ❌ The card was NOT tagged with cardPriority
• ❌ No priority was assigned
• The Rem needs manual investigation

How to fix:

1. Check the detailed error log in console
2. Look for the specific error message
3. Try to open the Rem manually in RemNote
4. If the Rem is accessible, you can manually set priority using Alt+P
5. Report the error details if it seems like a plugin bug

How to Investigate Errors

Step 1: Check the Console

After pre-computation, open your browser's Developer Console (F12) and look for:

=== DETAILED ERROR LOG ===
Total errors: 268

Error 1/268:
  RemId: abc123xyz
  Reason: Rem not found - may have been deleted
  
Error 2/268:
  RemId: def456uvw
  Reason: Exception during processing: Cannot read property 'text' of undefined
  Details: [error object]
  
...

Step 2: Get the List of Failed RemIds

At the end of the error log, you'll find:

=== FAILED REM IDs (for investigation) ===
abc123xyz
def456uvw
ghi789rst
...
=== END FAILED REM IDS ===

You can copy this list and:

1. Search for these Rems in RemNote
2. Check if they still exist
3. Manually assign priorities if needed

Step 3: Re-run Pre-computation

After fixing issues:

1. Run pre-computation again
2. Check if error count decreased
3. Most "Rem not found" errors should auto-resolve after card cleanup

Important Notes

Error Count vs Failed Tagging

• Error count = Rems that failed to process
• Newly tagged = Rems that were successfully tagged

When to Worry

• < 100 errors out of 10,000+ rems: Normal, likely deleted/orphaned cards
• > 1,000 errors: May indicate a systemic issue, investigate
• All errors are "exceptions": Likely a plugin bug, report it