When an import finds no trades, the file is empty, has only a header, has no readable trade rows, uses the wrong broker format, or every execution was already imported.
Empty file, zero bytes
Empty File — the file size is zero.
Fix: export again from your broker so the file includes trade data.
File has only a header row
The file has column headers but no trade rows.
Fix: re-export a date range that includes closed trades.
No data found in the CSV
No Data Found — the file is not empty, but no trade rows can be read.
Fix: confirm you are uploading the correct trade export for the broker you selected.
Import failed, file contains no trades
The parser ran, but no valid trades were in the export for that range.
Fix: export a wider date range, turn off filters on the broker export page, and confirm the export type is trades rather than orders.
Correct file type, but broker filters left the export empty
Fix: in your broker, clear filters, select the full range, export again.
Custom CSV, no valid trades found
Fix: open the CSV and confirm it has trade rows with valid data.
All executions were already imported
Every execution already exists in that trading account. Deduping skipped them on purpose.
Fix: check Settings > Import History for the Duplicates count.
TopstepX same-day export is empty
Fix: export from the Trades tab, not Orders. Widen the range: start yesterday, end two days from today.
Match Trader, wrong format or open positions first
Match Trader accepts HTML only, and closed positions must be uploaded before open positions.
Wrong file type or wrong broker format
Fix: in Add Trades, select the correct broker and re-export in the format it needs.
