Trades Not Syncing? Fix Broker Sync Issues
If your trading journal shows stale data or new executions from Zerodha, Fyers, Angel One, Upstox, or another supported broker are missing in TradeLyser, the problem is almost always fixable without losing history. This guide walks Indian traders through broker trade sync failures step by step: how to confirm whether sync actually ran, when to reconnect, how to use manual sync and CSV backup, and what information to send support if the issue persists.
TradeLyser imports executed trades from connected accounts. Pending orders, cancelled legs, and trades outside your selected date range will not appear until they meet import rules. Understanding that boundary saves hours of false troubleshooting.
Quick diagnosis: is it sync or a filter?
Before changing settings, answer these questions in under two minutes:
| What you see | Likely cause | First action |
|---|---|---|
| Account shows Disconnected or Authorization expired | OAuth or API session ended | Reconnect broker |
| Last synced timestamp is old but status is Connected | Auto-sync delayed or broker API slow | Manual sync |
| Sync succeeds but trade count is zero | No new executed trades in broker period | Verify executions in broker app |
| Trades exist in broker but not in TradeLyser | Date filter, wrong account, or partial import | Missing trades guide |
| Error in Sync History | Credentials, API limits, or broker outage | Read error text; follow sections below |
How broker sync works in TradeLyser
When you connect a broker, TradeLyser stores an authorization token (OAuth) or API credentials, depending on the integration. On a schedule and when you tap Sync Now, the platform requests completed orders and fills from the broker API, maps them to your journal format, and skips rows that match existing trades (duplicate protection).
What sync imports:
- Executed buy/sell legs with price, quantity, and timestamps
- Fees and charges when the broker exposes them
- Updates to positions that affect open P&L views
What sync does not import:
- Pending, rejected, or cancelled-only orders (until executed, if ever)
- Trades from accounts you have not connected
- Data the broker API does not expose for your plan or segment
For a full walkthrough of manual sync, see How to Sync Trades from Connected Broker.
Common causes and detailed fixes
1. Connection or authorization expired
Symptoms: Orange or red status on Settings → Accounts, banner asking you to reconnect, or sync jobs that fail immediately with auth errors.
Indian brokers that use daily OAuth (notably Zerodha Kite and Fyers) require you to re-approve access regularly—often once per trading day or after password changes. API-key brokers may need new keys if you rotated them in the broker portal without updating TradeLyser.
Fix:
- Open Settings → Accounts.
- Select the affected account → Reconnect (or disconnect and connect again using the correct broker guide).
- Complete the full broker login and consent screen; do not close the tab early.
- Run Sync Now and confirm Last synced updates.
Broker-specific connection guides: Zerodha, Fyers, Angel One, Upstox, 5Paisa.
If reconnect fails repeatedly, use Broker Connection Failed before escalating to support.
2. Broker API unavailable or rate-limited
Symptoms: Sync fails with timeout or generic API errors; broker mobile app also slow; social media posts about outages.
Brokers schedule maintenance around market open/close. During NSE/BSE holidays or heavy volatility, APIs can lag. TradeLyser will retry on the next sync, but you should not assume data loss until you verify the broker still lists the trades.
Fix:
- Log in to your broker website or app and confirm trade book / order history shows the executions.
- Check the broker’s status or Twitter/X support channel for maintenance.
- Wait 15–30 minutes and run Sync Now again.
- If the outage spans a full session, import that day via CSV so your journal stays complete.
3. Wrong date range or timezone perception
Symptoms: “Sync worked” but you only see older trades; intraday session seems empty.
TradeLyser displays timestamps in your configured timezone (typically IST). A trade executed at 23:55 or across midnight may appear on a different calendar day than you expect. Dashboard and Trades pages also honor date filters—a narrow range can look like sync failure.
Fix:
- On Trades, set the date filter to All time or include the session date.
- Confirm Settings → Trade Settings timezone is IST if you trade Indian markets.
- Re-run sync after the broker has finalized the contract note or trade book for that session.
4. Trades not yet executed in the broker
Symptoms: You placed orders but nothing new appears; open orders visible only in broker order pad.
Sync pulls fills, not working orders. AMO orders, GTT triggers, and partial fills may arrive in multiple import rows over time.
Fix:
- In the broker app, open Trade book / Order history and confirm status is COMPLETE or fully filled.
- Sync again after each fill if you scalp and need near-real-time journaling.
- For manual strategies not on the broker API, use manual trade entry.
5. Manual sync not run after heavy trading day
Symptoms: Auto-sync usually works; today’s session missing until you notice at night.
Auto-sync intervals depend on plan and broker. After an active day, a manual sync confirms completion before you review reports or AI analytics.
Fix:
- Settings → Accounts → ⋮ → Sync Now, or use the header Sync on the dashboard (sync guide).
- Open Sync History and verify Success with a non-zero import count.
- Spot-check the newest trade in Trades against the broker.
6. Duplicate protection hiding “missing” trades
Symptoms: You re-imported or synced the same session; count did not increase.
TradeLyser deduplicates on symbol, date/time, price, and quantity (and related keys). Re-syncing the same fill is expected to add zero rows.
Fix:
- Search Trades by symbol and session date—the trade may already exist.
- If a trade was edited incorrectly, fix via edit trade rather than forcing a duplicate import.
- For CSV re-import issues, see CSV Import Errors.
7. Multiple accounts: sync ran on the wrong account
Symptoms: Data looks fine on one profile but empty on another; mentor or multi-account setup.
Fix:
- Use the account switcher and confirm the active account matches the broker login you traded on (switch accounts).
- Sync each connected account from Settings → Accounts.
- Review connection status for every linked broker.
Step-by-step recovery workflow
Follow this order to avoid skipping the real root cause:
- Verify in broker — Executions exist in trade book.
- Check connection — Status Connected; reconnect if expired.
- Manual sync — Run once; note timestamp.
- Sync History — Read status and error message.
- Trades page — All time filter, correct account.
- CSV backup — Import gap days if API still down.
- Support — Send logs if steps 1–6 fail with evidence.
Broker-specific notes (India)
| Broker | Typical sync gotcha |
|---|---|
| Zerodha | Daily Kite login for OAuth; sync after logout/login if token stale |
| Fyers | Similar daily auth; verify API enabled in Fyers dashboard |
| Angel One | SmartAPI keys must match environment; check key expiry |
| Upstox | Redirect URL and API version must match portal setup |
| Dhan / Groww | Prefer CSV for historical gaps if API history window is short |
Detailed connection troubleshooting: Troubleshoot Broker Connection.
Prevention: keep sync reliable
- Reconnect after password changes or broker security resets.
- Run end-of-day manual sync before journaling and weekly reviews.
- Keep a CSV export habit for brokers with short API history windows.
- Monitor Sync History weekly for failed jobs.
- Avoid connecting the same broker login twice under different labels—it complicates deduplication.
Information to send support
Email support@tradelyser.com if sync fails after the workflow above. Include:
- Broker name and account type (equity/F&O)
- TradeLyser login email and affected account label
- Last successful sync time from Sync History
- Exact error text or screenshot
- One example trade (symbol, date, time) visible in broker but not in TradeLyser
- Whether OAuth reconnect temporarily fixed the issue
Pro users can also use in-app chat for faster turnaround.
Frequently asked questions
Why did sync work yesterday but not today?
Daily OAuth brokers require re-authorization. Start with Reconnect and manual sync.
Does TradeLyser sync open positions?
Yes, when the broker API exposes position updates; closed legs sync as trades. Open position views are covered in track live P&L.
How long should manual sync take?
Usually 10–30 seconds; large historical backfills can take several minutes. If it runs over 5 minutes with no Sync History update, refresh and retry once.
Will syncing twice duplicate my trades?
No—duplicate protection skips identical fills. Legitimate multi-fill scalps still import as separate rows when the broker sends them separately.
Can I sync while markets are open?
Yes. Intraday traders often sync after major positions close or at lunch break.
What if only F&O trades are missing?
Confirm the connected account includes the derivatives segment and that executions appear in the broker’s F&O trade book, not only the equity ledger.
Should I disconnect and reconnect often?
Only when auth fails or you change API keys. Unnecessary disconnects do not improve sync speed.
Is CSV import better than sync?
CSV is best for historical backfill or broker outages; ongoing journaling is easier with live sync plus occasional manual sync.