Interactive Brokers · Trader Workstation

Find the setting.
Understand the fix.

Clear TWS help for connection errors, missing quotes, order problems, and TradingView automation through PickMyTrade.

For education, not investment advice. Financial and information disclaimers.

105 guides

Connection and login

How to enable the TWS API for PickMyTrade

Turn on Enable ActiveX and Socket Clients in TWS, then match its socket port in PickMyTrade. The API is the local connection that lets the desktop app talk to TWS.

Read guide
Connection and login

Can IBKR Desktop replace TWS for PickMyTrade?

Follow the connection requirements for the PickMyTrade desktop app. A product named IBKR Desktop is not the same app as Trader Workstation.

Read guide
TradingView and PickMyTrade

Before resuming IBKR automation after a disconnect

Check broker state before allowing new signals. The app may have missed a status update even if the broker accepted the order.

Read guide
TradingView and PickMyTrade

Choose one clear exit workflow for PickMyTrade IBKR

Identify whether TradingView sends exits or PickMyTrade attaches broker-side stops and targets. Configure the documented mode with care.

Read guide
TradingView and PickMyTrade

Add or correct a missing IBKR symbol in PickMyTrade

Compare the app’s symbol settings with the exact TWS contract. Use PickMyTrade’s documented Create Settings workflow when a symbol is missing.

Read guide
TradingView and PickMyTrade

A paper test for TradingView to IBKR automation

Follow one paper signal from the chart to the broker record. Check the account, product, and size first.

Read guide
TradingView and PickMyTrade

IBKR order quantity differs from the TradingView alert

Trace size through the signal, account multiplier, contract mapping, and final broker order.

Read guide
Connection and login

TWS connects but orders fail: check Read-Only API

Read-Only API can allow an app to connect while blocking its trading requests. Find the setting under API → Settings.

Read guide
TradingView and PickMyTrade

PickMyTrade alert JSON is invalid: find the bad field

Use the current PickMyTrade IB alert form to create the message. Then read what the alert actually sent.

Read guide
TradingView and PickMyTrade

TradingView alert fired but no IBKR order appeared

Find the first missing stage. An alert firing, a webhook arriving, an app accepting it, and IBKR accepting an order are separate events.

Read guide
TradingView and PickMyTrade

TradingView alert still uses old strategy settings

A script alert uses a saved version of its setup when created. Editing the chart does not necessarily update that running alert.

Read guide
TradingView and PickMyTrade

TradingView backtest trades are not IBKR fills

TradingView’s strategy report shows model trades. TWS shows broker orders and fills. Start with a real alert in the log and trace that event.

Read guide
TradingView and PickMyTrade

Bar-close alerts versus intrabar IBKR execution

Check whether the script alerts during a bar or only after it closes. An intrabar signal can change before the candle finishes.

Read guide
TradingView and PickMyTrade

Duplicate IBKR orders: trace the original alerts

If two orders appear for one planned signal, trace both back to their alerts. Check for two active alerts, a repeated event, or a resend.

Read guide
TradingView and PickMyTrade

Strategy versus indicator alerts for IBKR automation

Choose the alert type that matches your script. A chart mark, an indicator condition, a script call, and a strategy fill are not the same event.

Read guide
TradingView and PickMyTrade

TradingView to IBKR through PickMyTrade: setup checks

For the desktop workflow, TradingView sends a webhook to PickMyTrade, and the PickMyTrade desktop app connects to TWS.

Read guide
TradingView and PickMyTrade

TradingView webhook delivery failed: check the cause

Read the Webhook status for the alert in TradingView. A domain, connection, or timeout failure happens before you can assume the broker received an order.

Read guide
TradingView and PickMyTrade

TradingView webhook timeout: verify before retrying

A timeout means TradingView did not receive a timely response; it does not by itself prove the receiver did nothing.

Read guide
Connection and login

TWS socket connects but the account never appears

A socket connection is only the first part of API startup. The app also needs the TWS handshake and account details.

Read guide
TWS settings and performance

TWS API Precautions: what bypass settings mean

API → Precautions lets you skip some order warnings. Read the full warning first. Find the one box that matches it and learn what the box skips.

Read guide
TWS settings and performance

TWS auto-lock and API availability

If the app stops after you leave TWS idle, check Lock and Exit. Also check whether the computer went to sleep. These are different controls.

Read guide
TWS settings and performance

Where to configure TWS Auto restart

Open Global Configuration → Lock and Exit to check the restart or logoff schedule. Choose a planned pause and check the next startup.

Read guide
Orders and exits

TWS bracket order is missing its stop or target

Check the complete parent-and-child order group. A filled entry does not prove both exits were accepted.

Read guide
Orders and exits

Cancel a TWS order and verify it really stopped

A cancel request is not the same as a confirmed cancellation. The order may fill before the cancel reaches the venue.

Read guide
Quotes and charts

TWS chart and API timestamps use different time zones

Record the time zone attached to each timestamp. The TWS operator time zone, an exchange time zone, and UTC can describe the same event with different clock times.

Read guide
Connection and login

TWS error 326: client ID already in use

Error 326 means another active API connection is using the same client ID. Find the duplicate app or assign a distinct supported ID.

Read guide
Contracts and account checks

TWS combo rejected: verify every spread leg

Read every leg of the spread: which contract, buy or sell, and how many. Then check the whole order’s route and price. One wrong leg changes the trade.

Read guide
Connection and login

TWS API connection approval popup: what to check

A TWS connection popup asks whether to accept an API client. Confirm the source belongs to the app you just opened. If no connection is expected, do not accept it.

Read guide
Contracts and account checks

Continuous futures symbols and TWS order routing

A continuous chart joins a series of futures months to show price history. It is not a full order destination. The app still needs a contract that can trade.

Read guide
Contracts and account checks

Find the contract multiplier before sizing an order

The contract multiplier helps turn a price move into a cash amount. Read it from the exact product in TWS. Do not assume two similar names use the same value.

Read guide
Error messages

TWS 2103 or 2105: a data farm disconnected

Check which data service disconnected and whether the break persists. A live-data service and a historical-data service have different roles.

Read guide
Error messages

TWS 2104, 2106 and 2158: connection OK messages

Messages 2104, 2106, and 2158 usually report successful connections to IBKR data services.

Read guide
Orders and exits

TWS DAY versus GTC: order duration explained

DAY and GTC tell TWS how long an order should stay working. They do not, on their own, say that it may trade outside normal hours.

Read guide
Quotes and charts

TWS delayed versus live data: how to tell

Check the quote’s data status before using its price. A moving number can still be delayed.

Read guide
Connection and login

Why TWS disconnects when you log in to TradingView

Check for competing IBKR trading sessions under the same username. A direct IBKR login in TradingView is different from a webhook sent to PickMyTrade.

Read guide
Contracts and account checks

TWS Download open orders on connection setting

Download open orders on connection helps expose order details when an API client connects. Review it with the app’s startup behavior.

Read guide
TWS settings and performance

How to enable TWS API logs for troubleshooting

TWS can record messages exchanged with an API client. Open API → Settings, enable Create API message log file, and use the requested logging level.

Read guide
Error messages

TWS error 100: too many API messages

Error 100 indicates the API client is sending messages too quickly. Stop a retry loop or request burst and have the app control its request rate.

Read guide
Error messages

TWS error 101: market-data line limit reached

Error 101 means the active market-data requests exceed the account’s available capacity. TWS windows and API clients can consume that capacity together.

Read guide
Error messages

TWS error 10197: competing market-data session

Error 10197 can mean that two sessions are trying to use the same live feed. This can affect a paper account that shares data with a live user.

Read guide
Error messages

TWS error 103: duplicate order ID

Error 103 points to an invalid reused or outdated order ID in the API client. Stop repeated retries and check the broker record first.

Read guide
Error messages

TWS error 110: price does not match the tick size

Error 110 means an order price does not fit the contract’s allowed price increment, also called its tick size. Check every price field, including the stop and limit.

Read guide
Error messages

TWS error 162: diagnose the historical data message

Error 162 is a historical-data service message with several possible causes. The text can describe missing permission, pacing, or unavailable data.

Read guide
Error messages

TWS error 200: contract not found or ambiguous

Error 200 means IBKR could not resolve the requested product to one contract.

Read guide
Error messages

TWS error 201: read the order rejection reason

Error 201 is an order rejection. The reason after the code is the useful part: it can point to permissions, funds, order size, price checks, or another rule.

Read guide
Error messages

TWS error 202: why was the order cancelled?

Error 202 reports an order cancellation. Check who or what requested it and whether any size filled first.

Read guide
Error messages

TWS error 321: request validation failed

Error 321 means a request did not pass validation. Read the accompanying text to find the field involved.

Read guide
Error messages

TWS error 354: market data is not subscribed

Error 354 points to missing market-data permission for the requested product. Check the exchange, product, username, and API data access.

Read guide
Connection and login

TWS error 502: cannot connect to the API

Error 502 means the app could not open its connection to TWS or IB Gateway. Start with the running program, host, and port.

Read guide
Error messages

TWS error 507 or EOF: the API socket closed

In a Java client, error 507 or an end-of-stream message can indicate that the socket connection broke.

Read guide
Orders and exits

Add an exit bracket to an existing TWS position

Start from the position you already hold to add a stop and target. Do not start with a new entry. First check whether there are exits for those shares or contracts.

Read guide
TWS settings and performance

Export TWS logs for an IBKR support case

Use TWS’s supported log-export process to obtain readable diagnostics. Keep the event time and the client ID with the case.

Read guide
Contracts and account checks

Find an instrument’s full contract details in TWS

Use Financial Instrument Info → Description on the product in TWS. Compare the complete contract, not just the ticker.

Read guide
Quotes and charts

TWS prices stop changing after the market closes

A closed market can leave last prices unchanged, and frozen data can show the last available values.

Read guide
Contracts and account checks

TradingView and TWS show different futures expiries

Check the full futures contract month that the app will trade. A chart may switch to a new month while your position stays in the old one.

Read guide
Contracts and account checks

Stock options versus futures options in TWS

An option on a future is not the same product type as an option on a stock. Find the full contract in TWS.

Read guide
TWS settings and performance

Check TWS futures order presets

Use Presets → Futures to check default contract count, order type, and timing. Confirm the specific futures contract as well.

Read guide
TWS settings and performance

Find Global Configuration in Mosaic and Classic TWS

In Mosaic, open File → Global Configuration. In Classic TWS, use Edit → Global Configuration.

Read guide
Quotes and charts

Why some historical data is unavailable in TWS

IBKR cannot supply every old price series. Check the product, dates, and bar size against its data limits.

Read guide
Quotes and charts

TWS historical-data pacing: stop repeated requests

Historical-data pacing limits how quickly an app can request bars. Repeating the same request at once can make the problem worse.

Read guide
TWS settings and performance

Review TWS hotkeys before using order shortcuts

TWS hotkeys can trigger actions quickly, including order-related actions. Review the command, scope, and any confirmation behavior in Global Configuration → Hotkeys.

Read guide
Error messages

TWS 2107 and 2108: inactive data farm messages

An inactive data-farm message can mean the service is idle until data is requested. It does not by itself show a broken connection.

Read guide
Orders and exits

TWS order is Inactive: find the actual reason

First check whether the order has been sent. IBKR’s status guide describes Inactive as an order being created but not yet activated or sent.

Read guide
Quotes and charts

TWS Level 1 versus Level 2 market data

Level 1 shows top-of-book prices. Level 2 adds market depth where supported and subscribed.

Read guide
Connection and login

TWS localhost and Trusted IPs explained

Localhost means the computer running the app. Trusted IPs tell TWS which remote source addresses it may accept.

Read guide
Connection and login

TWS disconnects after a Mac wakes from sleep

Sleep can interrupt the network connection used by TWS and its desktop client.

Read guide
Quotes and charts

Market data versus trading permissions in IBKR

Market-data permission controls the prices you receive. Trading permission controls the products you may trade.

Read guide
TWS settings and performance

How to check TWS memory allocation

TWS memory allocation is under Global Configuration → General. Increase it only when the workload and available computer memory justify the change.

Read guide
Contracts and account checks

Check micro versus standard futures before routing

A micro future and its larger version are two different contracts. Check the full product and size before you send an alert.

Read guide
Quotes and charts

TWS shows a last price but no bid or ask

A last price can remain visible even when no current bid or ask is available to your view. Check market hours, the exact contract, and subscription status.

Read guide
Orders and exits

Why an API app cannot modify a TWS order

API order management depends on the sending client and order binding. Seeing an order is not the same as being able to change it.

Read guide
Connection and login

TWS disconnects overnight: restart or connection loss?

Compare the disconnect time with TWS Lock and Exit settings and broker maintenance.

Read guide
Quotes and charts

TWS option chain loads but prices are blank

A populated chain shows contracts; it does not prove the account can receive quotes for each one.

Read guide
Contracts and account checks

Wrong option contract: check expiry, strike and right

An option needs more than an underlying symbol. Check expiry, strike, call or put, trading class, and multiplier.

Read guide
Quotes and charts

TWS option Greeks or implied volatility are missing

Live option Greeks need both option and underlying data. Also check that you selected a valid option with usable prices.

Read guide
TWS settings and performance

Check TWS option order presets and quantity

Use Presets → Options for option defaults, and confirm size is expressed in contracts. An option contract count is not a stock share count.

Read guide
Orders and exits

Use TWS Preview to inspect an order’s margin impact

Use Preview on a proposed TWS order to check estimated margin impact before sending. Confirm the contract and size first.

Read guide
TWS settings and performance

TWS Messages settings and order warnings

TWS Messages controls which notices appear. Read each message before changing it.

Read guide
Orders and exits

TWS order will not execute outside regular hours

Read the outside-hours field on the actual order. Then check that the product, venue, and order type can trade at that time. GTC alone is not enough.

Read guide
Orders and exits

IBKR overnight trading is not just an Outside RTH box

IBKR has special rules and routes for overnight trades. The Outside RTH box alone does not prove an app can send those trades.

Read guide
Orders and exits

Why TWS paper fills differ from live trading

Paper trading is a simulation. It is useful for checking setup and order handling, but its fills can differ from live execution.

Read guide
Connection and login

TWS and IB Gateway ports: paper versus live

The usual ports are 7497 for TWS paper, 7496 for TWS live, 4002 for IB Gateway paper, and 4001 for IB Gateway live. These are defaults.

Read guide
Quotes and charts

Paper TWS has no market data: what to check

A paper account does not automatically receive every live exchange feed. Check its data-sharing setup, the live user’s data access, and competing sessions.

Read guide
Orders and exits

TWS partial fill: check the remaining quantity

A partial fill means only part of the order executed. The remainder may still be working.

Read guide
Orders and exits

TWS order stuck on PendingSubmit

PendingSubmit means the order was sent but its destination has not yet confirmed acceptance. Check the connection, full status text, and any warning.

Read guide
Contracts and account checks

TWS and API P&L differ: compare the definitions

First name what each P&L number shows: today’s result, closed trades, or an open position. Match the account, product, currency, and time.

Read guide
Contracts and account checks

TWS position differs from the automation app

Reconcile a TWS position that differs from your automation app by checking the broker position and executions, then fix the cause safely.

Read guide
Quotes and charts

Why a TWS quote does not show every trade tick

A watchlist shows price updates at set intervals. It may not show every trade. Check which feed your app uses: standard quotes or tick-by-tick data.

Read guide
Quotes and charts

Quotes work in TWS but not through the API

Compare the API’s exact contract and data access with TWS. A quote visible in one interface does not prove the requested API feed is available.

Read guide
Connection and login

Connect a desktop app to TWS on a VPS

First decide whether the desktop app runs on the VPS with TWS or on a separate computer. Use localhost only for the same-machine case.

Read guide
TWS settings and performance

What to include in a TWS support request

A useful support case shows one symptom, its time, and the exact action that caused it.

Read guide
TWS settings and performance

Save or recover a TWS layout

Use TWS Layout Settings to save a known layout and recover one when windows move or disappear. Back up the current state before loading an older layout.

Read guide
TWS settings and performance

TWS is slow or freezing: a practical diagnosis

First find out what is slow: the TWS menus or the price feed. Try a small layout, then compare it with your usual set of windows.

Read guide
TWS settings and performance

Set stock order defaults in TWS Presets

TWS stock presets define defaults such as time in force, size, and primary order type. They are starting values, not proof of the final order.

Read guide
Contracts and account checks

Wrong stock listing in TWS: check primary exchange

A stock symbol may exist on more than one listing. Compare currency and primary exchange as well as the ticker.

Read guide
Orders and exits

Check the TWS stop trigger method

A simulated stop can use last price, bid/ask, or another supported trigger method. A chart touch does not necessarily meet that method’s conditions.

Read guide
Orders and exits

TWS stop versus stop-limit: why an exit may wait

A stop and a stop-limit are different instructions. A stop-limit adds a limit-price condition after its trigger, so triggering does not guarantee execution.

Read guide
Orders and exits

TWS says Submitted but the order has not filled

Submitted is an order state, not a fill receipt. Check the order’s limit price, market session, and remaining size.

Read guide
Contracts and account checks

TWS order rejected for trading permissions

Read why the broker refused the trade. If the account lacks the right to trade that product, check its approved permissions in Client Portal.

Read guide
Quotes and charts

Why TWS and TradingView candles differ

First check that both charts show the same product, month, time zone, and trading hours. Then check the kind of prices used.

Read guide
Connection and login

TWS versus IB Gateway for an API connection

TWS provides the full trading workspace. IB Gateway provides an API connection interface. Both require a broker login.

Read guide
Contracts and account checks

TWS virtual FX positions versus actual cash balances

A virtual FX position is a tracking view. It may not be your cash balance in that currency. TWS can include this view in API portfolio updates.

Read guide
Quotes and charts

TWS historical volume and VWAP differ from live data

IBKR documents filtering and adjustments in historical data that can make it differ from a live stream.

Read guide
Connection and login

TWS weekly login fails after automatic restart

An automatic restart may still require a fresh manual login during the weekly sign-in cycle.

Read guide
Contracts and account checks

PickMyTrade connects to the wrong IBKR account

Check the account returned by TWS and the account selected in the alert. They should be the same destination you meant to use.

Read guide

Financial and information disclaimers

Financial disclaimer

These guides explain software. They are for education, not financial, investment, tax, or legal advice. No example is a suggestion to buy or sell a product or use a trading strategy. Trading can lose money, including all funds you put at risk. With margin, futures, short sales, or some options, losses can exceed your starting funds. Automation can fail, send duplicate orders, or act late. Stops do not guarantee a fill or a price. Review your orders and positions, and seek advice from a qualified professional for your own needs. Paper trades, examples, and past results do not predict live results or promise a profit.

Information disclaimer

This is general help based on the sources and check date shown on the page. Screens, settings, fees, data access, and product support can change or differ by app version, account, country, and broker. The content may contain errors or become out of date; accuracy, completeness, and continuous service are not guaranteed. Check current broker and app instructions before acting. Screenshots show where controls are; they do not prove that an order test passed. This guide does not replace broker terms or risk notices. References to IBKR and TradingView identify their products and do not imply their endorsement of this guide.

IBKR risk disclosures · IBKR paper-trading limits · SEC guidance on automated investment tools

Automate TradingView alerts to Interactive Brokers

Connect TradingView to your IBKR account with PickMyTrade.

See the IBKR integration