When Leaf Edge refuses a file, leaves a row out or stops an IBKR Flex sync, it shows a code beside the reason. Find the code below for what happened and what to do next. Codes under Skipped on purpose are not errors.
If you write to us about one, include the code. Please never send a password, an account number or a whole broker statement.
Updated 1 November 2026.
The file was not imported
Leaf Edge refused the whole file, so nothing from it was imported.
EMPTY_FILEThe file is empty
- What happened
- The file has no content, so there was nothing to import. TradingView saves its Positions and Orders tabs as empty files when nothing is open.
- How to fix
- Upload the file that holds your trades. From TradingView, that is the Order History file; its name starts paper-trading-order-history.
Any broker · File upload
UNSUPPORTED_FORMATLeaf Edge doesn't recognise the file
- What happened
- The file isn't one of the exports Leaf Edge reads, so nothing was imported.
- How to fix
- Upload the file exactly as your broker exported it. A file opened and saved again in a spreadsheet can lose the columns Leaf Edge looks for. The Getting trades in guide lists the file each broker needs.
Any broker · File upload
FILE_TOO_LARGEThe file is too large
- What happened
- Leaf Edge imports files up to 4 MB.
- How to fix
- Export a shorter date range and import each file separately.
Any broker · File upload
TOO_MANY_ROWSThe file has too many rows
- What happened
- Leaf Edge imports up to 2,000 rows from one file.
- How to fix
- Export a shorter date range and import each file separately.
Any broker · File upload
MISSING_REQUIRED_COLUMNSColumns are missing
- What happened
- The file is missing columns Leaf Edge needs to read each trade. The message names them.
- How to fix
- Export the file again from your broker and upload it without removing or renaming any column.
Robinhood, Trading 212 · File upload
ACCOUNT_NUMBER_MISMATCHThe file is for a different account
- What happened
- The file states an account number that isn't the number of the account you chose. Joining them would put one account's trades in another's journal.
- How to fix
- Choose the account the file belongs to, or choose No account.
Interactive Brokers · File upload
ACCOUNT_BROKER_MISMATCHThe file is from a different broker
- What happened
- The account you chose belongs to another broker than the file, so the file can't join it.
- How to fix
- Choose one of that broker's accounts, or choose No account.
Any broker · File upload
TRADESVIZ_TRADES_EXPORTThis is TradesViz's Trades export
- What happened
- TradesViz's Trades export has one row per trade, not the individual fills Leaf Edge imports.
- How to fix
- In TradesViz go to Import, Manage/Export Data, choose your account, then Executions and Native / UTC. Upload that file.
TradesViz · File upload
TRADINGVIEW_WRONG_TABThis is the wrong TradingView file
- What happened
- TradingView's Export data saves each tab of the trading panel as its own file. This one is Balance History, Trade History or Activity Log, none of which lists your fills one by one.
- How to fix
- Upload the Order History file from the same export. Its name starts paper-trading-order-history.
TradingView · File upload
TRADING212_CFD_UNSUPPORTEDTrading 212 CFD accounts aren't supported
- What happened
- This is a Trading 212 CFD export. Its rows carry position results, currency conversion and financing, and importing them as share trades would give the wrong P&L, so none were imported.
- How to fix
- Export the history of your Trading 212 Invest or Stocks ISA account instead.
Trading 212 · File upload
IBKR_STATEMENT_NO_TRADESThe IBKR statement has no trades
- What happened
- This Interactive Brokers Activity Statement has no trades in its period.
- How to fix
- Download a statement for a longer period that includes your trades, or export them with a Flex Query.
Interactive Brokers · File upload
IBKR_STATEMENT_TRADES_UNREADABLEThe statement's trades can't be read
- What happened
- This Interactive Brokers Activity Statement has a Trades section, but Leaf Edge couldn't read a trade from it.
- How to fix
- Export your trades with a Flex Query instead.
Interactive Brokers · File upload
BROKER_SYNC_ONLYThis broker's files can't be imported yet
- What happened
- This looks like an export from Fidelity or E*TRADE, and Leaf Edge can't read their files yet.
- How to fix
- Connect the broker through read-only broker sync (SnapTrade) on the Pro or Ultimate plan, or add trades one at a time with Add Trade.
Fidelity, E*TRADE · File upload
NO_TRADE_ROWSThe file has no trade rows
- What happened
- Leaf Edge recognised the export, but it has no rows below its header.
- How to fix
- Check that the export covers a period with trades, then upload it again.
Any broker · File upload
NO_READABLE_ROWSNo row could be read
- What happened
- Leaf Edge recognised the export and it has rows, but none of them could be read as a trade.
- How to fix
- Upload the file exactly as your broker exported it. A file edited or saved again in a spreadsheet can change its dates and numbers so they no longer read.
Any broker · File upload
HTML_NOT_IBKR_STATEMENTThis HTML file isn't an IBKR statement
- What happened
- Leaf Edge reads an HTML file only as an Interactive Brokers Activity Statement, and this page isn't one.
- How to fix
- For any other broker, upload its CSV export instead.
Any broker · File upload
XML_NOT_FLEX_QUERYThis XML file isn't a Flex Query
- What happened
- Leaf Edge reads an XML file only as an Interactive Brokers Flex Query report, and this file isn't one.
- How to fix
- Run your Flex Query with the Trades section included and upload the XML it produces.
Interactive Brokers · File upload
MULTIPLE_ACCOUNTSThe file covers more than one account
- What happened
- The file holds trades for more than one IBKR account. A file joins one account, so nothing in it was imported.
- How to fix
- Export one account per file. In a Flex Query, select a single account before you run it.
Interactive Brokers · File upload
MALFORMED_CSVThe file's columns don't line up
- What happened
- A row has a different number of columns from the header, or the CSV can't be read, so nothing in the file was imported.
- How to fix
- Download the file from IBKR again and upload it unchanged. Saving it from a spreadsheet can move or merge columns.
Interactive Brokers · File upload
FLEX_TRADES_SECTION_INVALIDThe Flex file needs one complete Trades section
- What happened
- A Flex CSV file must hold exactly one Trades section, for one account, from its start marker to its end marker. This file has more than one, or a section that is cut short.
- How to fix
- Run the Flex Query for one account and upload the file it produces without editing it.
Interactive Brokers · File upload
OVERLAPPING_SECTIONSTrades and Trade Confirmations are both in the file
- What happened
- The Flex file has both a Trades and a Trade Confirmations section. They list the same fills, so importing both would count each fill twice. Nothing was imported.
- How to fix
- Export one execution section per file: Trades in your Activity Flex Query, or Trade Confirmations in a Trade Confirmation Flex Query.
Interactive Brokers · File upload
OPTION_LIFECYCLE_UNRECONCILEDOption exercises or expirations need their trades
- What happened
- The file has option exercise, assignment or expiration records without the matching execution-level trades. Leaf Edge doesn't guess how an option closed or which shares it delivered, so nothing was imported.
- How to fix
- Export the Trades section at execution level for the same period, so each exercise, assignment or expiration has its execution, then upload the new file.
Interactive Brokers · File upload
ACCOUNT_IDENTITY_CONFLICTA trade names another account than its statement
- What happened
- A trade in the Flex file names an account other than the statement it sits in, so nothing was imported.
- How to fix
- Run the Flex Query again for a single account and upload that file. If it keeps happening, contact support.
Interactive Brokers · File upload
SUMMARY_ROWS_ONLYThe file has summary rows, not executions
- What happened
- The Flex Query was run at summary level, and summary rows can't show your trades fill by fill.
- How to fix
- In the Flex Query's Trades section, choose execution-level detail, run it again and upload the new file.
Interactive Brokers · File upload
CANCELLATION_UNPAIREDA busted trade's original is missing
- What happened
- The file has IBKR's cancellation of a busted trade, but not the trade it cancels. Importing either one alone would invent a position or P&L, so nothing was imported.
- How to fix
- Export a date range that includes the original trade and upload it again. If it keeps happening, contact support.
Interactive Brokers · File upload
CANCELLATION_AMBIGUOUSA busted trade matches more than one fill
- What happened
- IBKR's cancellation of a busted trade matches more than one fill, so Leaf Edge can't tell which one IBKR cancelled. Nothing was imported.
- How to fix
- In your Flex Query, add the Orig Trade ID field, export again and upload the new file. If it keeps happening, contact support.
Interactive Brokers · File upload
A row was left out
Leaf Edge couldn't read the row as a trade. The preview counts it under Rejected; the rest of the file can still be imported. When every row of a file fails the same way, the file's layout is the likely cause, not your trades.
MISSING_SYMBOLThe row has no symbol
- What happened
- Leaf Edge can't tell which instrument the row traded, so the row was left out.
- How to fix
- If only some rows show this, check them in your broker's export. If the symbol is blank there too, add those trades with Add Trade.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Interactive Brokers, TradingView, TradesViz, Webull, tastytrade, Charles Schwab, Robinhood, Trading 212 · File upload
UNKNOWN_SIDEBuy or sell is missing
- What happened
- The row's side is blank or isn't a buy or a sell Leaf Edge recognises. Leaf Edge doesn't guess a trade's direction.
- How to fix
- If only some rows show this, check their side in your broker's export. A renamed or translated value isn't read.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name. If your platform is set to another language, export the file again in English first.
Interactive Brokers, TradingView, TradesViz, Webull, tastytrade, Trading 212 · File upload
INVALID_QUANTITYThe quantity is missing or zero
- What happened
- The row has no quantity Leaf Edge can read, or its quantity is zero.
- How to fix
- If only some rows show this, check their quantity in your broker's export. Upload the file exactly as your broker exported it.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Interactive Brokers, TradingView, TradesViz, Webull, tastytrade, Charles Schwab, Robinhood, Trading 212 · File upload
INVALID_PRICEThe price is missing, zero or negative
- What happened
- The row has no fill price Leaf Edge can read, or the price is zero or below zero. Leaf Edge doesn't import a fill at a made-up price.
- How to fix
- If only some rows show this, check their price in your broker's export. Upload the file exactly as your broker exported it.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Interactive Brokers, TradingView, TradesViz, Webull, tastytrade, Charles Schwab, Robinhood, Trading 212 · File upload
INVALID_DATEThe date is missing or unreadable
- What happened
- The row has no date and time Leaf Edge can read, so it can't be placed on your timeline.
- How to fix
- If only some rows show this, check their date and time in your broker's export. Upload the file exactly as your broker exported it.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Interactive Brokers, TradingView, TradesViz, Webull, tastytrade, Charles Schwab, Robinhood, Trading 212 · File upload
DATE_WITHOUT_TIME_ZONEThe time has no time zone
- What happened
- The row's time has no time zone, so it could land on the wrong day.
- How to fix
- Export Executions from TradesViz with Native / UTC, which writes each time with its offset.
TradesViz · File upload
INVALID_FEEA fee can't be read
- What happened
- The row has a commission or fee that isn't a number. Leaf Edge doesn't book an unreadable fee as zero.
- How to fix
- Upload the file exactly as your broker exported it. If the fee is unreadable there too, contact support with your broker's name.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
TradesViz, Charles Schwab · File upload
REPEATED_HEADER_ROWA header row repeats inside the file
- What happened
- A row partway through the file repeats the column names, usually because two exports were joined. It was left out.
- How to fix
- Nothing else in the file needs fixing. Next time, upload each export on its own.
TradingView · File upload
UNRECOGNISED_ROWThe row isn't a TradingView fill
- What happened
- The row has no order ID, trade ID or symbol, so nothing identifies it as a fill.
- How to fix
- Upload the Order History file as TradingView exported it. If the row looks like a fill there, contact support.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
TradingView · File upload
MISSING_EXECUTION_IDThe execution has no Trade ID
- What happened
- An IBKR execution has no Trade ID or Transaction ID, so Leaf Edge couldn't recognise it again on a later import. An order ID isn't an execution ID.
- How to fix
- Add Trade ID, and Transaction ID where it's offered, to the Trades section of your Flex Query, run it again and upload the new file.
Interactive Brokers · File upload
MISSING_COMMISSIONThe commission is missing
- What happened
- An IBKR execution has no Commission value Leaf Edge can read. Leaf Edge doesn't book a missing commission as zero.
- How to fix
- Add Commission (IB Commission in an Activity Flex Query) to the Trades section of your Flex Query, run it again and upload the new file.
Interactive Brokers · File upload
INCOMPLETE_OPTION_CONTRACTThe option contract is incomplete
- What happened
- An option row is missing its expiry, strike or put/call, so Leaf Edge can't tell which contract it traded.
- How to fix
- For IBKR, add Expiry, Strike and Put/Call to your Flex Query. For other brokers: upload the file exactly as your broker exported it.
Interactive Brokers, tastytrade, Charles Schwab · File upload
UNPARSEABLE_OPTION_SYMBOLThe option symbol can't be read
- What happened
- An Activity Statement option row's Symbol isn't in the form Leaf Edge reads (such as AAPL 06MAY26 270 P), so it was left out rather than imported without a strike and expiry.
- How to fix
- Export these trades with a Flex Query, which gives the option's expiry, strike and put/call fields of their own.
Interactive Brokers · File upload
ZERO_PRICE_FILLA fill is priced at zero
- What happened
- An Activity Statement row has no price, or a price of zero. A zero-priced stock fill or option opening would book a free position and corrupt your cost basis, so it was left out. Zero is accepted only when an option closes by expiry, assignment or exercise.
- How to fix
- Check the trade in IBKR. If it filled at a price, export it with a Flex Query.
Interactive Brokers · File upload
MISSING_OPEN_CLOSEThe open/close code is missing
- What happened
- An IBKR execution has no O (open) or C (close) code. Leaf Edge doesn't guess whether a fill opened or closed a position, because a wrong guess can invent profit.
- How to fix
- Add the Open/Close Indicator field to the Trades section of your Flex Query (on Trade Confirmations it is Code), run it again and upload the new file.
Interactive Brokers · File upload
INVALID_MULTIPLIERThe contract multiplier is missing or invalid
- What happened
- The row's contract multiplier is missing, zero or not a number. Options and futures need it to value each fill.
- How to fix
- For IBKR, add the Multiplier field to your Flex Query. For tastytrade, upload the export as tastytrade saved it, with its Multiplier column.
Interactive Brokers, tastytrade · File upload and IBKR Flex sync
CONTRACT_MULTIPLIER_MISMATCHOne contract shows two multipliers
- What happened
- Fills for the same contract show different multipliers, so Leaf Edge can't value them consistently. Those fills were left out.
- How to fix
- Check the contract in IBKR. If its multiplier changed after a corporate action, contact support with the symbol.
Interactive Brokers · File upload
INVALID_CURRENCYThe currency can't be read
- What happened
- The row's currency isn't a three-letter code such as USD.
- How to fix
- For IBKR, add the Currency field to your Flex Query. For tastytrade: upload the file exactly as your broker exported it.
Interactive Brokers, tastytrade · File upload
DUPLICATE_EXTERNAL_ID_CONFLICTOne trade ID, two different trades
- What happened
- The file uses the same trade ID for fills with different details, so Leaf Edge can't tell which is right. Those rows are left out, and when the check against your journal finds them, the file can't be committed until the export is fixed.
- How to fix
- Export the file again from your broker. If the rows still conflict, contact support with your broker's name.
Any broker · File upload
UNSUPPORTED_ASSET_CLASSThis asset class can't come from this export
- What happened
- The row's asset class isn't imported from this IBKR export. An Activity Statement doesn't carry the contract multiplier futures need, for example.
- How to fix
- From an Activity Statement, export these trades with a Flex Query instead. From a Flex Query, this asset class isn't imported yet.
Interactive Brokers · File upload
UNSUPPORTED_ASSETThis instrument isn't imported yet
- What happened
- Leaf Edge doesn't import this kind of instrument from this export yet, so the row was left out. From TradesViz, only stock rows import for now. From TradingView, a futures contract whose point value Leaf Edge doesn't know, or a currency pair it can't value in US dollars, is left out, and the row's message names it. So is an instrument in a connected broker's order history whose value the file's own closed P&L doesn't confirm, such as a CFD whose lot size its closes don't show.
- How to fix
- Nothing in the file needs changing. The trades left out can be added one at a time with Add Trade.
TradesViz, TradingView · File upload
UNSUPPORTED_POSITION_EVENTAssignments, exercises and splits aren't imported yet
- What happened
- The row changes a position without being a trade: an option assignment or exercise, a stock split, a share transfer, a merger and the like. Leaf Edge can't rebuild these yet, so that position may not match your broker. The row's message says what Leaf Edge does instead.
- How to fix
- Nothing in the file needs changing. Check the affected symbol against your broker.
tastytrade, Charles Schwab, Robinhood · File upload
ADJUSTED_OPTION_UNSUPPORTEDAdjusted options aren't supported
- What happened
- The option was adjusted by a corporate action, so its contract size isn't the standard 100 shares (or 10 for a mini option). Leaf Edge can't value it from the row alone.
- How to fix
- These rows can't be imported yet. Contact support with the symbol if you need them.
tastytrade · File upload
ORDER_FILLS_MISMATCHAn order's fills don't add up
- What happened
- In an IBKR Activity Statement, an order's Trade rows don't add up to the order's quantity, so Leaf Edge can't tell the fills apart safely. Neither the order nor its fills were imported.
- How to fix
- Import this period from a Flex Query instead.
Interactive Brokers · File upload
MISSING_PRICE_CURRENCYThe price's currency is missing
- What happened
- The row has a price but no currency for it, so Leaf Edge can't tell whether the price needs converting into your account's currency.
- How to fix
- Export the history from Trading 212 again with every column, and upload it unchanged.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Trading 212 · File upload
INVALID_EXCHANGE_RATEThe exchange rate is missing or invalid
- What happened
- The instrument trades in another currency than your account, and the row has no exchange rate Leaf Edge can use to convert its price.
- How to fix
- Export the history from Trading 212 again with every column, and upload it unchanged.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Trading 212 · File upload
INCONSISTENT_EXCHANGE_RATEThe exchange rate doesn't fit the currencies
- What happened
- The instrument trades in your account's currency, but the row shows an exchange rate other than 1, so its price can't be trusted.
- How to fix
- Upload the export exactly as Trading 212 saved it. If the row reads the same there, contact support.
- Every row shows it
- If every row in the file shows this, the likely cause is the file's layout, not your trades: Leaf Edge doesn't read this export's columns yet. That's on our side. Contact support with your broker's name.
Trading 212 · File upload
ROW_REJECTEDA row was refused without its own code
- What happened
- Leaf Edge refused the row without naming a cause. That shouldn't happen.
- How to fix
- Contact support with your broker's name and the reason shown on the row. Please never send the whole statement.
Any broker · File upload
A row clashes with your journal
The row was read, but it clashes with trades Leaf Edge already holds in a way it won't settle by guessing. The row was left out; the rest of the file can still be imported.
API_FACTS_DIFFERThe file disagrees with your IBKR sync
- What happened
- Your IBKR Flex sync already saved this execution, and the file shows different details for it. Leaf Edge keeps the sync's version and doesn't overwrite it from a file.
- How to fix
- If IBKR corrected the trade, run the sync again so it brings the correction. Otherwise nothing is missing: the trade is already in your journal.
Interactive Brokers · File upload
API_ORDER_FILLS_DIFFERThe file's fills differ from your IBKR sync
- What happened
- Your IBKR Flex sync already saved this order, and the file shows a changed or extra fill for it. Leaf Edge doesn't decide which fill is right.
- How to fix
- Run the sync again so it brings any correction, then preview the file again. If it keeps happening, contact support.
Interactive Brokers · File upload
EXECUTION_IN_OTHER_ACCOUNTThis trade belongs to another account
- What happened
- A trade with the same broker ID is already in another of your accounts.
- How to fix
- Choose the account the trade was first imported into. If the two accounts are really one, contact support.
Any broker · File upload
UPLOAD_MATCHES_CONNECTED_ACCOUNTThese trades belong to a connected account
- What happened
- No account was chosen for the file, and its trades match trades a broker connection already brought into one of your accounts. Leaf Edge won't add them again outside that account, so they aren't counted twice.
- How to fix
- Choose the connected account for this file and preview it again.
Any broker · File upload
AMBIGUOUS_API_MATCHSeveral synced fills match one row
- What happened
- More than one fill from your IBKR Flex sync matches this row, so Leaf Edge can't tell which one it is. The row was left out so nothing is counted twice.
- How to fix
- Contact support with the symbol and the date.
Interactive Brokers · File upload
API_CONTRACT_MISMATCHCurrency or contract size differs from your IBKR sync
- What happened
- The row looks like a fill your IBKR Flex sync saved, but its currency or contract size differs, so Leaf Edge didn't treat them as one fill.
- How to fix
- Check the row's currency and multiplier against IBKR. Contact support if the synced version is wrong.
Interactive Brokers · File upload
FILE_IDENTITY_CONFLICTAn earlier import's record is missing
- What happened
- The record Leaf Edge kept when it first matched this row to your IBKR sync is missing, or two rows claim it.
- How to fix
- Contact support with the import's date from Import history. Please don't delete trades to work around it.
Interactive Brokers · File upload
SNAPTRADE_DAYS_OVERLAPSnapTrade already imports this day
- What happened
- Your SnapTrade connection already imports this broker account on this date. Leaf Edge brings each account in through one connection so trades aren't counted twice.
- How to fix
- Leave these days to SnapTrade. Rows on other dates still import.
Any broker · File upload
ROW_NOT_CLASSIFIEDA row couldn't be checked against your journal
- What happened
- Something went wrong while Leaf Edge compared the row with your journal, so it was left out.
- How to fix
- Preview the file again. If the row is refused again, contact support with your broker's name and the reason shown.
Any broker · File upload
Skipped on purpose
These rows are not errors. Leaf Edge leaves them out by design and counts them under Skipped, so you can still see them.
ORDER_NOT_FILLEDThe order didn't fill
- What happened
- The order was cancelled, rejected or never filled, so there's no execution to import. It's listed with its status, not counted as an error.
- How to fix
- Nothing to fix.
TradingView, Webull · File upload
EXCLUDED_ASSET_CLASSCurrency conversions and CFDs are skipped
- What happened
- The row is a currency conversion, or a CFD in an Activity Statement. Leaf Edge doesn't track either as a position, so the row is skipped by design.
- How to fix
- Nothing to fix.
Interactive Brokers · File upload
NON_EXECUTION_SKIPPEDExpirations and dividend reinvestments are skipped
- What happened
- The row is an option expiration or a dividend reinvestment. Leaf Edge closes an expired option at $0 on its own, and a reinvested dividend isn't a trading decision.
- How to fix
- Nothing to fix.
tastytrade, Charles Schwab, Robinhood · File upload
CANCELLED_TRADE_PAIRA busted trade and its cancellation are skipped
- What happened
- IBKR cancelled (busted) this trade. The fill and IBKR's cancellation of it were both left out, so the bust adds no position and no P&L.
- How to fix
- Nothing to fix.
Interactive Brokers · File upload
The import stopped
Something other than the file's contents stopped the preview or the save. Nothing was imported unless the message says trades were saved.
PREVIEW_EXPIREDThe preview is no longer open
- What happened
- This preview was cancelled, committed or closed before Commit reached it.
- How to fix
- Upload the file again to make a new preview.
Any broker · File upload
PREVIEW_RECEIPT_INVALIDThe stored preview can't be used
- What happened
- The copy of the file kept for this preview is missing or no longer matches what you previewed, so nothing was imported.
- How to fix
- Upload the file again to make a new preview.
Any broker · File upload
PREVIEW_ACCOUNT_CHANGEDThe account changed after the preview
- What happened
- The account this preview joins is no longer the one shown, or no longer exists.
- How to fix
- Upload the file again and choose the account in the new preview.
Any broker · File upload
COMMIT_CONFLICTYour journal changed during the import
- What happened
- A trade or account changed while the import was being saved, so nothing was imported.
- How to fix
- Try again. If it happens again, upload the file again to make a fresh preview first.
Any broker · File upload
LEDGER_CONFLICTThe import conflicts with your journal
- What happened
- Saving these trades would conflict with trades already in your journal, so nothing was imported.
- How to fix
- Contact support with the import's date. Please don't delete trades to work around it.
Any broker · File upload
LEDGER_REBUILD_FAILEDTrades saved, but your totals weren't rebuilt
- What happened
- The trades were saved, but rebuilding your journal's totals failed, so the import wasn't marked complete.
- How to fix
- Don't import the same trades again. Contact support with the recovery batch or sync time shown in the message.
Any broker · File upload and IBKR Flex sync
IMPORT_NOT_FINALIZEDTrades saved, but the import wasn't closed
- What happened
- The trades were saved, but the import couldn't be marked complete.
- How to fix
- Don't import the file again. Contact support with the recovery batch shown in the message.
Any broker · File upload
COMMIT_TIMEOUTSaving took too long
- What happened
- Saving this import took too long, so nothing was imported.
- How to fix
- Try again. If it keeps happening, import a shorter date range.
Any broker · File upload
COMMIT_FAILEDThe import couldn't be saved
- What happened
- Something went wrong while saving, and nothing was imported.
- How to fix
- Try again in a moment. If it keeps happening, contact support.
Any broker · File upload
SYNC_IN_PROGRESSAnother import is running
- What happened
- Another import or sync of your account is running. Leaf Edge runs one at a time so trades aren't counted twice.
- How to fix
- Wait for it to finish, then try again.
Any broker · File upload and IBKR Flex sync
SNAPTRADE_SYNC_RUNNINGA SnapTrade sync of this broker is running
- What happened
- SnapTrade is syncing this broker for you right now, so nothing was imported.
- How to fix
- Wait for the SnapTrade sync to finish, then preview the file or run the sync again.
Any broker · File upload and IBKR Flex sync
INVALID_REQUESTThe request couldn't be read
- What happened
- The import or sync request was missing something Leaf Edge needs.
- How to fix
- Reload the page and try again. If it keeps happening, contact support.
Any broker · File upload and IBKR Flex sync
UNKNOWNSomething went wrong on our side
- What happened
- The import or sync stopped on an error Leaf Edge didn't expect.
- How to fix
- Try again in a moment. If it keeps happening, contact support.
Any broker · File upload and IBKR Flex sync
IBKR Flex sync
Fast Sync or Full Sync stopped. When IBKR answers with one of its own error numbers, the message on the Sync page shows that number too.
IBKR_FLEX_NOT_READYIBKR hasn't finished the statement
- What happened
- IBKR couldn't send the report yet: its statement or P&L data isn't ready, or it is still being generated.
- How to fix
- Wait a few minutes, then run the sync again.
Interactive Brokers · IBKR Flex sync · IBKR error 1001, 1004, 1005, 1006, 1007, 1008, 1019, 1021
IBKR_FLEX_STATEMENT_UNAVAILABLEIBKR has no statement to send
- What happened
- IBKR says the statement isn't available.
- How to fix
- Run the query once from IBKR's Flex Queries page. If IBKR can't produce it there either, check the query's period and account selection. If it runs there but the sync still fails, contact support.
Interactive Brokers · IBKR Flex sync · IBKR error 1003
IBKR_FLEX_SERVER_BUSYIBKR is busy
- What happened
- IBKR's report service is under heavy load and couldn't generate the statement.
- How to fix
- Try again in a few minutes.
Interactive Brokers · IBKR Flex sync · IBKR error 1009
IBKR_FLEX_LEGACY_QUERYLegacy Flex Queries no longer run
- What happened
- IBKR no longer runs legacy Flex Queries.
- How to fix
- Create an Activity Flex Query (and a Trade Confirmation Flex Query for Fast Sync) in IBKR, then save the new Query IDs in Leaf Edge under Sync, Use API Keys.
Interactive Brokers · IBKR Flex sync · IBKR error 1010
IBKR_FLEX_SERVICE_INACTIVEIBKR says the service account is inactive
- What happened
- IBKR says the account behind this Flex token is inactive for the Flex Web Service.
- How to fix
- On IBKR's Flex Queries page, open Flex Web Service Configuration, check that Flex Web Service is enabled, and save. Then run the sync again.
Interactive Brokers · IBKR Flex sync · IBKR error 1011
IBKR_FLEX_TOKEN_EXPIREDThe Flex token has expired
- What happened
- IBKR says the Flex Web Service token has expired.
- How to fix
- On IBKR's Flex Queries page, open Flex Web Service Configuration and generate a new token. Then save it in Leaf Edge under Sync, Use API Keys. Then run the sync again.
Interactive Brokers · IBKR Flex sync · IBKR error 1012
IBKR_FLEX_IP_RESTRICTEDThe token has an IP restriction
- What happened
- IBKR refused the request because the token only accepts requests from the IP addresses set on it. Requests come from Leaf Edge's servers, not your own browser.
- How to fix
- Contact support before you change the restriction.
Interactive Brokers · IBKR Flex sync · IBKR error 1013
IBKR_FLEX_QUERY_INVALIDIBKR doesn't accept the Query ID
- What happened
- IBKR says the Flex Query is invalid.
- How to fix
- Copy the Query ID again from IBKR's Flex Queries page and save it in Leaf Edge under Sync, Use API Keys: the Activity query for Full Sync, the Trade Confirmation query for Fast Sync. Then run the sync again.
Interactive Brokers · IBKR Flex sync · IBKR error 1014
IBKR_FLEX_TOKEN_INVALIDIBKR doesn't accept the token
- What happened
- IBKR says the Flex token is invalid.
- How to fix
- Copy the Current Token again from Flex Web Service Configuration in IBKR, or generate a new one, and save it in Leaf Edge under Sync, Use API Keys. Then run the sync again.
Interactive Brokers · IBKR Flex sync · IBKR error 1015
IBKR_FLEX_ACCOUNT_INVALIDIBKR says the account is invalid
- What happened
- IBKR says the account in this request is invalid.
- How to fix
- Check the account selected in both Flex Queries in IBKR, and the IBKR account number saved in Leaf Edge. Then run the sync again.
Interactive Brokers · IBKR Flex sync · IBKR error 1016
IBKR_FLEX_REFERENCE_INVALIDIBKR lost track of the report
- What happened
- IBKR says the reference for the report Leaf Edge asked it to build is invalid.
- How to fix
- Run the sync again; each sync asks IBKR for a new report. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync · IBKR error 1017
IBKR_FLEX_RATE_LIMITEDToo many requests for this token
- What happened
- IBKR allows each Flex token one request a second and 10 a minute, and this token reached the limit.
- How to fix
- Wait a minute, then run the sync again. Linked accounts share one token, so sync them one at a time, and don't use the token in another app at the same time.
Interactive Brokers · IBKR Flex sync · IBKR error 1018
IBKR_FLEX_REQUEST_INVALIDIBKR couldn't validate the request
- What happened
- IBKR says the request is invalid or couldn't be validated.
- How to fix
- Check the Flex token and Query ID saved in Leaf Edge under Sync, Use API Keys. Then run the sync again. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync · IBKR error 1020
IBKR_FLEX_TOO_MANY_FAILURESToo many failed attempts
- What happened
- IBKR stopped accepting requests from this token after too many failed attempts.
- How to fix
- Fix the cause of the earlier failures first, usually the token or the Query ID, then wait before you try again. If you need a new token: on IBKR's Flex Queries page, open Flex Web Service Configuration and generate a new token. Then save it in Leaf Edge under Sync, Use API Keys.
Interactive Brokers · IBKR Flex sync · IBKR error 1025
IBKR_REPORT_REJECTEDIBKR rejected the report request
- What happened
- IBKR refused the request with an error number Leaf Edge has no entry for yet. The message shows the number when IBKR sends one.
- How to fix
- Check the Flex token, the Query ID and the query's account selection in IBKR. Look the number up in IBKR's Flex Web Service error list, or contact support with it.
Interactive Brokers · IBKR Flex sync
IBKR_TIMEOUTIBKR took too long
- What happened
- IBKR didn't finish the report within the time a sync can wait.
- How to fix
- Try again in a few minutes.
Interactive Brokers · IBKR Flex sync
TIMEOUTThe sync timed out
- What happened
- IBKR didn't answer in time, or its report wasn't ready before the sync had to stop.
- How to fix
- Try again in a few minutes.
Interactive Brokers · IBKR Flex sync
IBKR_TOKEN_BUSYAnother account is using this token
- What happened
- Linked IBKR accounts share one Flex token, and another account's sync is using it now.
- How to fix
- Wait for that sync to finish, then run this one.
Interactive Brokers · IBKR Flex sync
IBKR_REPORT_REVIEWThe report has rows that need review
- What happened
- IBKR sent the report, but some executions are missing fields Leaf Edge needs (the message names them), or option records need their trades. No executions from this report were saved.
- How to fix
- Add the named fields to the Flex Query in IBKR, under Sections, Trades or Trade Confirmations, then run the sync again. Import history keeps the report and each refused row.
Interactive Brokers · IBKR Flex sync
IBKR_SYNC_FAILEDThe IBKR sync didn't finish
- What happened
- Something went wrong talking to IBKR or reading its report, and the import didn't complete.
- How to fix
- Check the sync's receipt in Import history, then try again. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync
IBKR_JOURNAL_ACCOUNT_MISMATCHThis journal belongs to another IBKR account
- What happened
- This connection is already bound to a different IBKR account number than the one now saved in its settings. Nothing was imported.
- How to fix
- Restore the account number saved for this connection, or add a separate journal account for the other IBKR account.
Interactive Brokers · IBKR Flex sync
IBKR_ACCOUNT_NOT_IN_REPORTThe report doesn't include your account
- What happened
- The Flex report doesn't contain the IBKR account this connection imports. Nothing was imported.
- How to fix
- In IBKR, check the account selected in both saved Flex Queries. Then run the sync again.
Interactive Brokers · IBKR Flex sync
IBKR_ONE_ACCOUNT_REQUIREDThe report must cover one account
- What happened
- The Flex report covers more than one IBKR account, or names none, so Leaf Edge can't tell which account to import. Nothing was imported.
- How to fix
- Select exactly one account in the Flex Query. If the query includes linked accounts, enter the intended IBKR account number in Leaf Edge under Sync, Use API Keys.
Interactive Brokers · IBKR Flex sync
IBKR_PLAN_REQUIREDIBKR sync needs Pro or Ultimate
- What happened
- Syncing IBKR with Flex is part of the Pro and Ultimate plans.
- How to fix
- Upgrade to sync IBKR directly, or export a Flex Query file and upload it, which works on every plan.
Interactive Brokers · IBKR Flex sync
IBKR_CREDENTIALS_MISSINGNo IBKR credentials are saved
- What happened
- This connection has no saved Flex token and Query ID.
- How to fix
- Open Sync, Use API Keys, enter the Flex token and both Query IDs, and save.
Interactive Brokers · IBKR Flex sync
IBKR_QUERY_ID_MISSINGThe Query ID for this sync is missing
- What happened
- Full Sync uses the Activity Flex Query and Fast Sync the Trade Confirmation Flex Query, and the one this sync needs isn't saved.
- How to fix
- Open Sync, Use API Keys, add the missing Query ID and save.
Interactive Brokers · IBKR Flex sync
CREDENTIALS_UNREADABLESaved credentials can't be read
- What happened
- Leaf Edge couldn't read the Flex credentials saved for this connection.
- How to fix
- Enter the Flex token and Query IDs again under Sync, Use API Keys, and save.
Interactive Brokers · IBKR Flex sync
CREDENTIALS_UNAVAILABLESaved credentials are unavailable
- What happened
- Leaf Edge can't open saved credentials right now. The problem is on our side.
- How to fix
- Try again later. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync
CREDENTIALS_EXPIREDIBKR refused the credentials
- What happened
- IBKR answered that the request wasn't authorised.
- How to fix
- Check the Flex token and Query IDs under Sync, Use API Keys. If the token has expired, generate a new one in IBKR's Flex Web Service Configuration.
Interactive Brokers · IBKR Flex sync
RATE_LIMIT_EXCEEDEDIBKR is limiting requests
- What happened
- IBKR answered that too many requests were made.
- How to fix
- Wait a minute, then run the sync again.
Interactive Brokers · IBKR Flex sync
RATE_LIMITEDToo many syncs in a minute
- What happened
- Leaf Edge runs up to 5 IBKR syncs a minute for each account and sync type.
- How to fix
- Wait for the time shown in the message, then try again.
Interactive Brokers · IBKR Flex sync
MAINTENANCEIBKR is down for maintenance
- What happened
- IBKR's report service is down or under maintenance.
- How to fix
- Try again later.
Interactive Brokers · IBKR Flex sync
CIRCUIT_OPENIBKR syncs are paused
- What happened
- After several IBKR errors in a row, Leaf Edge pauses IBKR syncs for a few minutes. The message says when they resume.
- How to fix
- Wait for the time shown in the message, then try again.
Interactive Brokers · IBKR Flex sync
ACCOUNT_NOT_FOUNDThe account wasn't found
- What happened
- The broker account for this sync no longer exists in Leaf Edge.
- How to fix
- Reload the Sync page and choose the account again.
Interactive Brokers · IBKR Flex sync
ACCOUNT_LIMITYour plan's account limit is reached
- What happened
- Your plan's broker account limit has been reached, so the IBKR account couldn't be added.
- How to fix
- Remove an account you no longer use, or move to a plan with more broker accounts.
Interactive Brokers · IBKR Flex sync
ACCOUNT_MISMATCHThe report belongs to another account
- What happened
- The IBKR report belongs to a different account than this connection. Nothing was imported.
- How to fix
- Check the account selected in both Flex Queries and the IBKR account number saved in Leaf Edge.
Interactive Brokers · IBKR Flex sync
ACCOUNT_CHANGEDThe account changed during the sync
- What happened
- The account's details changed while the import was being prepared, so nothing was imported.
- How to fix
- Run the sync again.
Interactive Brokers · IBKR Flex sync
BATCH_CHANGEDThe sync's receipt went missing
- What happened
- The receipt Leaf Edge opened for this sync was no longer there when it came to save.
- How to fix
- Run the sync again. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync
BOOK_CHANGEDYour journal changed during the sync
- What happened
- Trades this sync was about to update changed while it was saving, so nothing was imported.
- How to fix
- Run the sync again. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync
BUSTED_FILL_IN_JOURNALIBKR cancelled a fill that's already in your journal
- What happened
- IBKR busted (cancelled) a fill after it had been imported, so your journal holds a trade that didn't happen. Nothing from the report was imported, so the cancelled fill isn't counted twice.
- How to fix
- Contact support to remove the cancelled fill, then run the sync again.
Interactive Brokers · IBKR Flex sync
IBKR_EXCLUDED_CLASS_HELDYour journal holds trades this sync leaves out
- What happened
- An earlier import brought in an asset class the IBKR sync leaves out, so the report can't skip it without making those positions wrong. The message names the asset class. Nothing was saved.
- How to fix
- Contact support with the account and the asset class named in the message.
Interactive Brokers · IBKR Flex sync
SNAPTRADE_ALSO_CONNECTEDSnapTrade already imports this account
- What happened
- This IBKR account is already connected through SnapTrade, or the report's trades were already imported through it. Leaf Edge brings each account in through one connection so trades aren't counted twice.
- How to fix
- Use one connection for the account: keep SnapTrade, or remove its SnapTrade connection before syncing with Flex.
Interactive Brokers · IBKR Flex sync
SNAPTRADE_CONNECTED_ACCOUNTThis account is connected through SnapTrade
- What happened
- The Leaf Edge account you chose is connected through SnapTrade, so a Flex sync can't import into it. Nothing was imported.
- How to fix
- Sync this account through SnapTrade, or add a separate account for the Flex connection.
Interactive Brokers · IBKR Flex sync
INCOMPLETE_SOURCEThe broker's records need review
- What happened
- The broker sent records that need review, or its history isn't complete yet. No executions from the batch were saved.
- How to fix
- Read the refused rows in Import history, fix the report at your broker and run the sync again.
Interactive Brokers · IBKR Flex sync
INVALID_EXECUTIONAn execution can't be read
- What happened
- An execution in the report is missing its ID, symbol or time, or has an invalid price, quantity, side or fee. Nothing was imported.
- How to fix
- Check that the Flex Query includes Trade ID, Symbol, Date/Time, Buy/Sell, Quantity, Price and Commission, then run the sync again.
Interactive Brokers · IBKR Flex sync
MISSING_CURRENCYAn execution has no currency
- What happened
- An execution in the report is missing its currency. Nothing was imported.
- How to fix
- Add the Currency field to the Flex Query. Then run the sync again.
Interactive Brokers · IBKR Flex sync
MISSING_MULTIPLIERA futures execution has no multiplier
- What happened
- A futures execution in the report is missing its contract multiplier, which its P&L depends on. Nothing was imported.
- How to fix
- Add the Multiplier field to the Flex Query. Then run the sync again.
Interactive Brokers · IBKR Flex sync
INVALID_OPTION_CONTRACTAn option execution is incomplete
- What happened
- An option execution in the report is missing its expiry, strike, put/call or multiplier. Nothing was imported.
- How to fix
- Add Expiry, Strike, Put/Call and Multiplier to the Flex Query. Then run the sync again.
Interactive Brokers · IBKR Flex sync
UNSUPPORTED_PRECISIONA number is too precise to store
- What happened
- An execution has a value with more digits than your journal can store exactly, so nothing was imported. The report was kept for review.
- How to fix
- Contact support with the symbol and the date.
Interactive Brokers · IBKR Flex sync
CONFLICTING_IDENTITYOne execution ID, two different fills
- What happened
- The report uses the same execution ID for fills with different details. Nothing was imported.
- How to fix
- Run the sync again. If it keeps happening, contact support.
Interactive Brokers · IBKR Flex sync
AMBIGUOUS_IDENTITYEarlier import records conflict
- What happened
- Leaf Edge holds conflicting records of which fill an execution is, so it won't guess. Nothing was imported.
- How to fix
- Contact support with the date of the sync from Import history.
Interactive Brokers · IBKR Flex sync
REUSED_EXECUTION_ALIASTwo fills share one execution ID
- What happened
- Different fills in the report share an execution ID, so Leaf Edge can't keep them apart. Nothing was imported.
- How to fix
- Contact support with the date of the sync from Import history.
Interactive Brokers · IBKR Flex sync
REUSED_EXECUTIONTwo fills claim one journal trade
- What happened
- Different fills in the report match the same trade in your journal. Nothing was imported.
- How to fix
- Contact support with the date of the sync from Import history.
Interactive Brokers · IBKR Flex sync
LEGACY_ORDER_IDAn older import used an order ID
- What happened
- An earlier import stored this order under its order ID rather than its fills, so the fills can't be matched to it yet. Nothing was imported.
- How to fix
- Contact support so the older record can be reconciled.
Interactive Brokers · IBKR Flex sync
MISSING_CLAIM_TARGETAn earlier journal record is missing
- What happened
- An execution's earlier record in your journal is missing. Nothing was imported.
- How to fix
- Contact support with the date of the sync from Import history.
Interactive Brokers · IBKR Flex sync
ACCOUNT_COLLISIONAn execution belongs to another account
- What happened
- An execution ID in the report is already assigned to another of your accounts. Nothing was imported.
- How to fix
- Check that this connection imports the right IBKR account. Contact support if the accounts are really one.
Interactive Brokers · IBKR Flex sync
AMBIGUOUS_ORDER_OVERLAPAn uploaded file shows this order differently
- What happened
- A file you uploaded earlier shows this order with different fills, and Leaf Edge won't decide which is right. Nothing was imported.
- How to fix
- Contact support with the order's symbol and date.
Interactive Brokers · IBKR Flex sync
AMBIGUOUS_OVERLAPSeveral uploaded fills match one synced fill
- What happened
- More than one fill from files you uploaded matches one fill in the report. Nothing was imported.
- How to fix
- Contact support with the fill's symbol and date.
Interactive Brokers · IBKR Flex sync
MISSING_FILE_IDENTITYAn uploaded fill's record is missing
- What happened
- A fill you uploaded earlier matches this report, but its import record can't be used. Nothing was imported.
- How to fix
- Contact support with the fill's symbol and date.
Interactive Brokers · IBKR Flex sync
INVALID_FILE_IDENTITYRecords of uploaded fills need review
- What happened
- The records Leaf Edge keeps of fills you uploaded need review before a sync can match against them. Nothing was imported.
- How to fix
- Contact support with the date of the sync from Import history.
Interactive Brokers · IBKR Flex sync