Trades Not Showing After Import

4 min readUpdated March 15, 2026

Trades Not Showing After Import

If you have imported trades via CSV or connected an exchange via API and your trades are not appearing, work through the following checklist. Most issues are caused by date filters, sync delays, or import format problems.

Quick Checklist

  1. Is the sync still in progress?
  2. Are you looking at the correct date range?
  3. Are you looking at the correct exchange account?
  4. Did the import complete without errors?
  5. Is the CSV in the correct format?

Step-by-Step Troubleshooting

1

Check If Sync Is Still Running

After connecting a new exchange or uploading a CSV, TraderNest needs time to process the data. Look for a loading indicator or "Syncing..." message on the Trades page or in SettingsExchanges. For large accounts with thousands of trades, the initial sync can take several minutes. Wait for the sync to complete before investigating further.

2

Check Your Date Range Filter

This is the most common reason trades appear to be missing. The Trades page has a date range selector at the top. If the selected range does not include the dates of your imported trades, they will not appear in the list.

Solution: Set the date range to "All Time" or manually expand it to cover the period of the trades you imported. On the Free plan, you are limited to 3 months of history — trades older than 3 months will not appear until you upgrade.

3

Check the Correct Exchange Account

If you have multiple exchange accounts connected, make sure you are viewing the right one. The Trades page may have an exchange filter dropdown. Check that it is set to "All Exchanges" or specifically to the exchange you just connected.

4

Check Connection Status (API Sync)

If you connected via API, go to SettingsExchanges and check the status of your connection. You should see one of the following:

  1. Connected (green) — The connection is active and syncing correctly.
  2. Syncing (blue/loading) — The initial sync is in progress.
  3. Error (red) — There is a problem with the connection. Click on the error to see details. Common causes include expired API keys, IP whitelist issues, or incorrect permissions.
5

Check CSV Format (CSV Import)

If you imported via CSV and no trades appeared, the most likely cause is a format mismatch. Common issues:

  1. Wrong export type: You may have exported the wrong data from your exchange. For example, on Kraken, you need to export "Trades" or "Ledgers", not "Orders".
  2. Wrong date format: The CSV date format might not match what TraderNest expects. TraderNest supports most common formats (YYYY-MM-DD, MM/DD/YYYY, DD/MM/YYYY) but unusual formats may not parse correctly.
  3. Wrong delimiter: TraderNest expects comma-separated values. If your CSV uses semicolons (common in some European locales), it may not parse correctly.
  4. Missing required columns: The CSV must contain the minimum required columns for the selected exchange format.

Solution: Re-export from your exchange following the specific steps in the relevant help article (e.g., "Importing Trades via CSV (Kraken)"). Make sure to select the correct export format.

6

Refresh the Page

Sometimes the trade list does not update automatically after an import completes. Try a hard refresh: press Ctrl + Shift + R (Windows/Linux) or Cmd + Shift + R (Mac) to force a full page reload.

7

Check for Futures vs. Spot

TraderNest is designed for crypto futures trading. If your API key only has spot trading permissions (not futures/derivatives), TraderNest will connect successfully but find no futures trades to import. Go back to your exchange and ensure your API key has Futures or Derivatives read permissions enabled.

Still not working? If you have worked through all these steps and trades are still not showing, contact us at [email protected] with the following information: your exchange name, whether you used API or CSV, the date range of the trades you expect to see, and any error messages you received. We will investigate and get back to you within 24 hours.

Did this answer your question?