Add troubleshooting and decoding info

.vitepress/config.mts

@@ -79,6 +79,7 @@ export default defineConfig({
       {
         text: 'Advanced',
         items: [
+          { text: 'Troubleshooting', link: '/usage-guides/troubleshooting' },
           { text: 'Set the backend\'s arguments', link: '/usage-guides/backend-arguments' },
           { text: 'rotki data directory', link: '/usage-guides/data-directory' },
           { text: 'Accessing the database manually', link: '/usage-guides/accessing-db-manually' },

usage-guides/historical-events.md

@@ -80,23 +80,43 @@ Refreshes events from specific protocols such as Monerium and Gnosis Pay, pullin
 
 ## Redecoding blockchain transactions
 
-It is possible that you need to redecode events for blockchain transactions (EVM and Solana). To do that you have two options. The first of them is to click on the three-dots `⋮` menu to display the options for an transaction and click on `Redecode events`. This will start the process to read the transaction's events again and try to understand what happened in them. If there are any custom events in the transaction, there will be one more confirmation, asking whether to also reset these custom events or not.
+Sometimes you may need to redecode events for blockchain transactions (EVM and Solana).
 
-![Redecode events for an transaction](/images/redecode_events.png)
+### Redecode a single transaction
 
-The second option is to redecode all transactions that have been queried. To do so you need to click on `Redecode All Transactions` at the top of the page.
+1. Click the three-dots `⋮` menu on the transaction row
+2. Click `Redecode events`
+
+This will re-read and re-decode the transaction's events and try to understand what happened. If the transaction contains custom events, you will get an extra confirmation asking whether to also reset these custom events.
+
+![Redecode events for a transaction](/images/redecode_events.png)
+
+::: tip Advanced: Redecode with options
+If you need more control, use `Redecode with options` (button at the right of `Redecode events`) to:
+
+- Select how custom events should be handled by the redecoding logic
+- Choose the priority for indexers that we want to use when re-querying remote information about the transaction
+  :::
+
+### Redecode all queried transactions
+
+To redecode all transactions that have been queried, click `Redecode All Transactions` at the top of the page.
 
 ![Menu to redecode all queried EVM transactions events](/images/redecode_all_events.png)
 
-To see the status of the event's decoding, you can click the menu button and go to `Transaction Decoding Status.`
+### Transaction decoding status
+
+To see the status of event decoding, click the menu button and go to `Transaction Decoding Status`.
 
 ![Menu to redecode events for an EVM transaction](/images/redecode_events_status_button.png)
 
 You will see the status of the EVM events redecoding.
 
 ![EVM events redecoding breakdown](/images/redecode_events_status.png)
 
-EVM Transactions and the events can be deleted, but to restore them you will have to either purge all transactions or add by the transaction hash.
+### Notes
+
+EVM transactions and events can be deleted, but to restore them you will have to either purge all transactions or add by the transaction hash.
 
 ![History events query status](/images/events_filter.png)
 

usage-guides/troubleshooting.md

@@ -0,0 +1,58 @@
+# Troubleshooting
+
+## Invalid input error during login
+
+These errors happen due to an invalid value in the frontend settings
+While the should not typically happen, it can occur due to a bug in the frontend.
+
+The error appears as a red alert in the page with a message like this:.
+
+![Redecode events for a transaction](/images/ts_profit_loss.png)
+
+In this case, the problem is with the `'profitLossReportPeriod'`, so to fix it,
+you need to modify the `profit_loss_report_period/` field in the frontend settings.
+
+To do so:
+
+1. Open the browser developer tools and go to the Console.
+   - Ctrl + Shift + I on Windows/Linux
+   - Cmd + Option + I (⌘ + ⌥ + I) on macOS
+2. Then proceed to modify the part of the code that sets the value of the field. Paste it in the console and run it.
+
+For example to fix the `profitLossReportPeriod` field you would need to run the following code:
+
+```js
+/* eslint-disable unicorn/prefer-top-level-await */
+fetch('http://127.0.0.1:4242/api/1/settings')
+  .then(response => response.json()) // Parse JSON response
+  .then((data) => {
+    const result = data.result;
+    const frontend_settings = result.frontend_settings;
+    const parsed = JSON.parse(frontend_settings);
+    parsed.profit_loss_report_period = {
+      quarter: 'ALL',
+      year: '2025',
+    };
+    const stringified = JSON.stringify(parsed);
+
+    fetch('http://127.0.0.1:4242/api/1/settings', {
+      method: 'PUT',
+      headers: {
+        'Content-Type': 'application/json',
+      },
+      body: JSON.stringify({
+        settings: {
+          frontend_settings: stringified,
+        },
+      }),
+      mode: 'cors', // Enable CORS
+    });
+  })
+  .catch((error) => {
+    console.error('Error:', error);
+  });
+```
+
+::: tip
+You can also use the same approach to modify other values in the settings by changing the fields in `parsed` and sending them back with the `PUT` request.
+:::