Skip to main content

Troubleshooting Interactive Brokers (IBKR) Sync Issues

Fix common IBKR sync issues in TradeZella — same-day trades not importing, reconnection prompts, configuration errors, and failed connections.

Written by Team

Having trouble connecting or re-linking your Interactive Brokers account with TradeZella? Here are the most common issues and how to fix them.

My trades from today aren't importing

If your account is connected but trades only show up the next day, you're likely missing a Trade Confirmation Flex Query — this is the query that enables same-day imports.

Head to the Add Trade page, click the three-dots menu next to your IBKR account, and update your sync settings to add your Trade Confirmation Flex Query ID. If you haven't created one yet, follow the steps in our IBKR sync guide

I keep getting asked to reconnect my account

This usually means your Flex Token expired. Log in to IBKR, go to Performance & Reports > Flex Queries, and check your Flex Web Service token — make sure the activation period is set to 365 days.

If it's shorter, generate a new token and update it in TradeZella through the three-dots menu on the Add Trade page.

I'm getting a configuration error, or my account connects but no trades import

First, check the Import History page to see if any errors are showing. Then verify your queries in IBKR under Performance & Reports > Flex Queries:

  • Activity Flex Query — in the Sections area, Trades should be selected with Executions and Select All checked. Leave all other settings as default.

  • Trade Confirmation Flex QueryExecutions should be selected with Select All checked, and the format set to CSV. Leave everything else as default.

If you previously customized settings (like date or time formats) for an older version of our sync, the easiest fix is to delete the query and recreate it with default settings following our IBKR sync guide, then reconnect your account in TradeZella.

Double-check your IDs

Make sure each ID went into its matching field — the Flex Token is the long one, and the Activity Flex Query ID and Trade Confirmation Query ID are short numeric IDs. Swapped IDs are one of the most common causes of failed connections.

Still stuck?

Reach out to our support team with:

  • A screenshot of your Flex Token activation period

  • Screenshots of both your Activity and Trade Confirmation query configurations

We'll take it from there!

Did this answer your question?