Trandence

Import History lets you audit every import job après le fichier has been processed. Utilisez it when you need to confirm what was created, understet 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 le newest import first et includes:

  • Date: when le job started
  • Source: CSV upload, Broker Sync, or manual entry
  • Broker: le broker attached to le import
  • File: le original source fichier name when disponibles
  • Status: terminés, 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 tableau is paginated et prend en charge 10, 15, 25, or 50 rows per page.

Filters

Utilisez filters to narrow le 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 après typing to apply le search

Utilisez Clear to reset every filter et return to le newest imports.

Status Meanings

StatusMeaning
COMPLETEDThe import finished successfully.
PARTIALSome données was imported, but some rows or sessions were skipped or failed. Vérifiez details avant re-importing.
FAILEDThe job did not complete successfully. Open details et export le report if support needs le failure context.
PROCESSINGThe import is still running or was last recorded in progress.
PENDINGThe job was created but processing has not started yet.

A PARTIAL import is often le most important one to inspect, because it may have created valid trades while skipping conflicts or invalid rows.

Job Details

Cliquez sur a row or le eye icon to open Import Job Details.

The detail dialog montre:

  • status, source, broker, timezone, fichier name, start time, finish time, et duration
  • created, skipped by validation, skipped by conflict, et failed counts
  • error breakdown grouped by reason
  • imported sessions, including session date, trade count, final P&L, et open-position marker

Utilisez this dialog to answer questions like:

  • Did le fichier use le expected timezone?
  • Which sessions were imported?
  • Were rows skipped because they were invalid or because they conflicted with existing données?
  • Did any imported session include open positions?

Export Report

Utilisez le download icon or Export Report in le detail dialog to download a support report for le sélectionné import.

The report includes:

  • import details
  • résumé counts
  • date range
  • error reasons
  • session-level results et warnings

The exported report is useful when comparing import attempts or sending support le relevant import context without sharing le full broker export.

When To Re-import

Before re-importing, check le reason for skips or failures:

  • Si rows were skipped by validation, fix le source fichier, broker selection, or timezone.
  • Si rows were skipped by conflict, review le existing trades avant trying again.
  • Si le job failed, export le report et keep le original broker fichier unchanged for troubleshooting.

For le import workflow itself, see Importing Trades. For connected-broker imports, see Broker Sync.


Besoin d’aide ?

Si an import job is failed or partial et le report is unclear, send le exported JSON plus broker name, fichier type, et timezone to [email protected].