Troubleshooting & Common Fixes
This page covers common issues you may encounter with the tradeGIST add-on and provides step-by-step solutions. If you can't resolve an issue, check the FAQ or report it via the add-on's help menu.
Prices not updating
- Symptoms: Current prices remain blank or outdated after running "Update prices."
- Causes: Incorrect API keys, invalid symbols, or API limits.
- Solutions:
- Verify your API keys in the ⚙️ Settings dialog → External API keys section (CoinMarketCap for crypto, Massive.com for options). The Test button next to each key checks it with a single lightweight request (no portfolio data fetched). For options, ensure you have at least an "Options Starter" subscription (or superior) from Massive.com to fetch live snapshot prices.
- Check asset symbols for accuracy (e.g., "BTC" for Bitcoin).
- Run "Update prices" manually and wait for completion.
- For equities, refresh the page to get the latest
GOOGLEFINANCEvalue.GOOGLEFINANCEupdates prices approximately every minute. You can also set your spreadsheet setting "recalculation" to "On change and every minute".
- Example: If BTC prices don't update, confirm your CMC API key is active and the symbol is "BTC".
- Prevention: Test API keys periodically and avoid exceeding rate limits.
API errors or rate limits
- Symptoms: Error messages like "API key invalid" or "Rate limit exceeded."
- Causes: Expired keys, incorrect setup, or high usage.
- Solutions:
- Regenerate API keys from the provider (CoinMarketCap or Massive.com).
- Update the keys in the ⚙️ Settings dialog (External API keys section) and save.
- Reduce update frequency or upgrade to paid API plans for higher limits.
- Example: If Massive.com returns a rate limit error, wait a few minutes or switch to a higher limit subscription.
- Prevention: Monitor usage on provider dashboards and refresh prices at reasonable intervals.
Calculation errors in trades
- Symptoms: Incorrect P/L, unmatched trades, or
#ERROR!in cells. - Causes: Data entry mistakes, mismatched currencies, or formula issues.
- Solutions:
- Review trade entries in the Transactions sheet for accuracy (dates, quantities, prices).
- Ensure your base currency is set correctly in the ⚙️ Settings dialog.
- Run "Generate trades" after fixes and check for errors.
- For tax calculations, verify rates in Configuration match your jurisdiction.
- Example: If a sell trade shows wrong gains, confirm the buy trades are entered and matched via FIFO/LIFO.
- Prevention: Double-check entries in your Transactions sheet.
It's possible for an asset to increase in value (e.g., TSLA went from $200 to $250), but if the currency conversion rate decreased during the same period, it could result in an overall negative ROI and a loss for the trade.
Snapshot failures
- Symptoms: No daily snapshots or errors in logs.
- Causes: Automated snapshots disabled, incorrect hour setting, or permission issues.
- Solutions:
- Confirm Automated snapshots is enabled and the Daily snapshot hour is a valid 24-hour time in the ⚙️ Settings dialog (and that your changes are saved).
- Ensure assets have "Take snapshot" checked.
- Example: If snapshots miss at 9 AM, verify Automated snapshots is on and the hour is set to 9.
- Prevention: Test snapshots manually and review logs for patterns.
The snapshot hour is set in GMT. Adjust for your timezone (e.g., 16:00 in New York is 20:00 or 21:00 GMT depending on daylight saving).
Chart display problems
- Symptoms: Charts not updating or showing incorrect data.
- Causes: Configuration mismatches or data issues.
- Solutions:
- Adjust "Lookup days" or "Num assets" in the Dashboard tab of the ⚙️ Settings dialog.
- Ensure snapshots are current and assets are included.
- Ensure every cell in the Snapshot sheet has a value. If you started trading an asset after your earliest snapshots were taken, make sure that the "value", "shares", and "price" columns for those older rows contain a "0". Fill in any blank cells with "0" manually.
- Example: If the ROI chart misses assets, increase "Num assets" in the Dashboard tab of the ⚙️ Settings dialog.
- Prevention: Keep Configuration settings aligned with your portfolio size.
#N/A returned from CURR_RATE_AT custom function
Under the hood, the =CURR_RATE_AT(<currency>, <date>) formula relies on GOOGLEFINANCE, which is unfortunately not always reliable and consistent.
If #N/A is returned by the =CURR_RATE_AT(<currency>, <date>) formula:
- Try refreshing the page to see if the value updates.
- Change the date to one day later, wait for the new value, then revert to the correct date—hopefully the value appears.
- If neither works, manually enter the conversion rate for that specific date.
General tips
- Backups: Regularly make a backup copy of your sheet (File > Make a copy) to avoid data loss.
- Updates: The add-on updates automatically — Google rolls out new versions to your installation, so there's nothing for you to do.
- Support: For unresolved issues, provide your support key (which you can find in the ⚙️ Settings dialog → App information tab) and details when contacting support.
If these steps don't help, refer to the FAQ.