Skip to main content

Missing Trades After Import? Find & Restore

Few things are more stressful than knowing you traded a session but your trading journal looks empty. Missing trades after import or sync are usually caused by filters, wrong account context, incomplete broker exports, or pending orders—not permanent data loss. This guide gives Indian traders a structured search and recovery process before contacting support.

Use this page after CSV import or broker sync when counts do not match expectations.


First: confirm they are truly missing

Answer these before deeper fixes:

  1. Does the broker trade book show the executions as filled?
  2. Did Sync History or import summary report success with a trade count?
  3. Are you on the correct account and date range in TradeLyser?
  4. Could the trades already exist under another symbol spelling or duplicate skip?

Many “missing” cases are hidden by filters or already imported.


Quick visibility checklist

CheckSet to
Date filter on Trades / DashboardAll time or include session date
Account selectorCorrect broker account or All accounts
SearchSymbol as broker shows (e.g. full NFO name)
Import logSuccess with non-zero count
Broker statusExecuted, not pending

Why trades appear missing

1. Date filter active

Symptoms: Older history visible; today blank; weekly review shows gaps.

Causes: Dashboard or Trades page limited to “This week,” custom range, or fiscal quarter.

Fix:

  1. Open Trades → expand date filter → All time.
  2. On Dashboard, reset widget date scope if applicable (refresh dashboard).
  3. Remember IST session boundaries for overnight trades (trade settings).

2. Wrong account selected

Symptoms: Trades exist in one linked broker but not while another is active.

Causes: Multiple brokers; paper vs live mislabel; mentee vs own account.

Fix:

  1. Use account switcher → select the broker you traded (switch accounts).
  2. Try All accounts view when searching.
  3. Sync each account from Settings → Accounts (sync broker trades).

3. Import or sync partially failed

Symptoms: Import “succeeded” but count lower than broker; Sync History shows warnings.

Causes: Invalid rows in CSV; API timeout mid-batch; auth expired mid-sync.

Fix:

  1. Open Sync History or import summary—note errors.
  2. Fix source file per CSV import errors.
  3. Re-import only the missing date range to avoid duplicate anxiety (dedup will skip existing).
  4. Reconnect broker if auth failed (connection failed).

4. Trades not executed in broker

Symptoms: Order visible in order book; nothing in TradeLyser.

Causes: Pending, cancelled, or rejected orders; AMO not triggered.

Fix:

  1. Confirm trade book shows completed fills.
  2. Sync again after execution.
  3. Do not expect journal entries for cancelled scalps unless you manual entry for planning notes.

5. Duplicate protection skipped re-import

Symptoms: Second import adds zero rows; you expected more.

Causes: Trades already present from earlier sync; overlapping CSV.

Fix:

  1. Search by symbol + date.
  2. If trade exists but wrong, edit instead of re-import.
  3. If truly absent, check import used correct broker template.

6. Broker history window too short

Symptoms: Recent trades appear; old years missing.

Causes: API sync only pulls limited lookback; never imported CSV history.

Fix:

  1. Export full history from broker portal.
  2. Import in chunks via import CSV and sync historical trades.
  3. Broker guides: Zerodha history.

7. Segment or product not connected

Symptoms: Equity trades present; F&O missing.

Causes: Account connection without derivatives permission; export equity-only file.

Fix:

  1. Verify broker profile includes F&O segment.
  2. Re-export including derivatives.
  3. Reconnect with correct account type.

8. Deleted or archived by mistake

Symptoms: Trades were visible yesterday.

Causes: Accidental delete trade; wrong bulk operation.

Fix:

  1. Check if bulk delete was run (bulk operations).
  2. Restore from new CSV export of that period if deletion is irreversible.
  3. Contact support immediately with timeframe if account-wide loss suspected.

Recovery workflow

Broker trade book count

Sync History / import log count

TradeLyser All time + correct account

Symbol search

Re-sync or CSV gap fill

P&L spot check (1 trade)

Reconciling counts

SourceWhat to count
BrokerExecuted fills for date range (not order count)
Import logRows accepted + skipped duplicates
TradeLyserTrades list with same filters

Small differences are normal when:

  • Broker shows one aggregated line and TradeLyser shows split fills
  • Charges-only rows appear in broker reports but not as trades

Large differences (>5% of session trades) warrant CSV re-export.


Preventing missing trades going forward

  • Run end-of-day manual sync (sync guide).
  • Keep weekly CSV backup from broker.
  • Avoid aggressive date filters during review.
  • Label multiple accounts clearly (multiple accounts).
  • Monitor sync history for failed jobs.

Impact on analytics when trades are missing

Incomplete data depresses or inflates:

Backfill before making major strategy decisions.


Support escalation

Email support@tradelyser.com with:

  • Date range and broker
  • Expected trade count vs TradeLyser count
  • Sync History screenshot or import summary
  • Example symbol missing in TradeLyser but visible in broker (screenshot both)

Contact Support for response times by plan.


Frequently asked questions

I imported 500 trades but see 480—are 20 missing?

They may be duplicates skipped, failed rows, or outside your date filter. Check import log and All time view.

Can mentors see missing trades on mentee accounts?

Mentees must sync/import on their account; mentors see what exists after permissions (mentee access).

Do open positions count as trades?

Open positions appear in open positions; closed round trips appear in Trades.

Will historical sync delete old trades?

Normal sync and import add or skip duplicates; they do not wipe the journal unless you delete.

Mobile app missing trades?

Ensure mobile uses same account; pull to refresh; web may sync first (mobile trades).

Missing one leg of a hedge?

Import both legs; search each symbol separately.


Search techniques on the Trades page

When you believe a trade exists but cannot see it:

  1. Use symbol search with the exact broker scrip name (including -EQ, expiry, or strike for derivatives).
  2. Try alternate spellings the broker uses (NIFTY24MAY vs NIFTY 24 MAY FUT).
  3. Sort by P&L or quantity to surface outliers in a busy day.
  4. Remove strategy or tag filters applied in a previous review session.
  5. Export or view trades log if your workflow uses list filters.

If search finds the trade, the issue was visibility—not import failure.


Working with mentors and shared accounts

Mentors only see data the mentee has synced and permitted. If trades are “missing” on the mentor view:

  • Mentee must complete import/sync on their login.
  • Permissions must include the relevant account (manage mentee permissions).
  • Mentee should verify All time before a review call.

Mentors should not import CSV into a mentee account without explicit agreement—use documented mentee workflows.


Calendar and journal cross-checks

Sometimes trades exist in Trades but appear missing from Daily Journal or calendar heatmaps because those views filter by journal assignment or session rules.

  • Add trades to journal per add trades to journal.
  • Open trading calendar with the same date scope as Trades.
  • Distinguish “no trade data” from “trade not linked to journal entry.”

Long-term archive strategy

For multi-year histories:

Year rangeSuggested approach
Current FYLive sync + weekly CSV backup
Prior 1–2 FYCSV chunks by quarter
OlderOne-time bulk import; label account “Archive FY20-21”

Archived accounts keep dashboards fast while preserving auditability. Use sync historical trades when broker API allows backfill.


Same-day options and multi-leg strategies

Options traders often look for one “strategy P&L” row while the journal lists each leg separately. If legs seem missing:

  1. Search each symbol (underlying and contract name).
  2. Confirm both buy and sell legs executed—half-completed spreads may show only one side until closed.
  3. Tag related legs with a shared strategy name in strategy board for grouped review.

Missing legs are frequently still in Trades under a different contract name than you searched.


Audit log habits for active traders

If you trade more than twenty times per day, adopt a daily close ritual:

  1. Run manual sync.
  2. Confirm today’s trade count in Trades vs broker trade book.
  3. Note count in your daily journal.

Catching a missing session the same evening is far easier than reconstructing a week from contract notes during tax season.