Import History lets you audit every import job after the file has been processed. Use it when you need to confirm what was created, understand skipped rows, investigate failures, or export an import report for support.
Open it from Trades -> History.
What The Table Shows
Each row represents one import job. The list is sorted with the newest import first and includes:
- Date: when the job started
- Source: CSV upload, Broker Sync, or manual entry
- Broker: the broker attached to the import
- File: the original source file name when available
- Status: completed, partial, failed, processing, or pending
- Created: number of trades created
- Skipped: validation skips plus conflict skips
- Failed: number of trades that failed during processing
- Actions: export report or open details
The table is paginated and supports 10, 15, 25, or 50 rows per page.
Filters
Use filters to narrow the import list:
- Date range: filters by import start time
- Status: all statuses or one status
- Source: all sources, CSV, Broker Sync, or Manual
- Broker: all brokers or one broker
- File name search: press Enter after typing to apply the search
Use Clear to reset every filter and return to the newest imports.
Status Meanings
| Status | Meaning |
|---|---|
| COMPLETED | The import finished successfully. |
| PARTIAL | Some data was imported, but some rows or sessions were skipped or failed. Review details before re-importing. |
| FAILED | The job did not complete successfully. Open details and export the report if support needs the failure context. |
| PROCESSING | The import is still running or was last recorded in progress. |
| PENDING | The job was created but processing has not started yet. |
A PARTIAL import is often the most important one to inspect, because it may have created valid trades while skipping conflicts or invalid rows.
Job Details
Click a row or the eye icon to open Import Job Details.
The detail dialog shows:
- status, source, broker, timezone, file name, start time, finish time, and duration
- created, skipped by validation, skipped by conflict, and failed counts
- error breakdown grouped by reason
- imported sessions, including session date, trade count, final P&L, and open-position marker
Use this dialog to answer questions like:
- Did the file use the expected timezone?
- Which sessions were imported?
- Were rows skipped because they were invalid or because they conflicted with existing data?
- Did any imported session include open positions?
Export Report
Use the download icon or Export Report in the detail dialog to download a support report for the selected import.
The report includes:
- import details
- summary counts
- date range
- error reasons
- session-level results and warnings
The exported report is useful when comparing import attempts or sending support the relevant import context without sharing the full broker export.
When To Re-import
Before re-importing, check the reason for skips or failures:
- If rows were skipped by validation, fix the source file, broker selection, or timezone.
- If rows were skipped by conflict, review the existing trades before trying again.
- If the job failed, export the report and keep the original broker file unchanged for troubleshooting.
For the import workflow itself, see Importing Trades. For connected-broker imports, see Broker Sync.
Need Help?
If an import job is failed or partial and the report is unclear, send the exported JSON plus broker name, file type, and timezone to [email protected].