Import History lets you audit every import job dopo il file has been processed. Usa it when you need to confirm what was created, underste 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 il newest import first e includes:
- Date: when il job started
- Source: CSV upload, Broker Sync, or manual entry
- Broker: il broker attached to il import
- File: il original source file name when disponibili
- Status: completati, 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 tabella is paginated e supporta 10, 15, 25, or 50 rows per pagina.
Filters
Usa filters to narrow il 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 dopo typing to apply il search
Usa Clear to reset every filter e return to il newest imports.
Status Meanings
| Status | Meaning |
|---|---|
| COMPLETED | The import finished successfully. |
| PARTIAL | Some dati was imported, but some rows or sessiones were skipped or failed. Rivedi details prima re-importing. |
| FAILED | The job did not complete successfully. Open details e export il report if support needs il 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 il most importante one to inspect, because it may have created valid trades while skipping conflicts or invalid rows.
Job Details
Fai clic su a row or il eye icon to open Import Job Details.
The detail dialog mostra:
- status, source, broker, timezone, file name, start time, finish time, e duration
- created, skipped by validation, skipped by conflict, e failed counts
- error breakdown grouped by reason
- imported sessiones, including sessione date, trade count, final P&L, e open-position marker
Usa this dialog to answer questions like:
- Did il file use il expected timezone?
- Which sessiones were imported?
- Were rows skipped because they were invalid or because they conflicted with existing dati?
- Did any imported sessione include open positions?
Export Report
Usa il download icon or Export Report in il detail dialog to download a support report for il selezionato import.
The report includes:
- import details
- riepilogo counts
- date range
- error reasons
- sessione-level results e warnings
The exported report is useful when comparing import attempts or sending support il relevant import context without sharing il full broker export.
When To Re-import
Before re-importing, check il reason for skips or failures:
- Se rows were skipped by validation, fix il source file, broker selection, or timezone.
- Se rows were skipped by conflict, review il existing trades prima trying again.
- Se il job failed, export il report e keep il original broker file unchanged for troubleshooting.
For il import workflow itself, see Importing Trades. For connected-broker imports, see Broker Sync.
Serve aiuto?
Se an import job is failed or partial e il report is unclear, send il exported JSON plus broker name, file type, e timezone to [email protected].