TWS 2107 and 2108: inactive data farm messages

Quick answer

An inactive data-farm message can mean the service is idle until data is requested. It does not by itself show a broken connection. Look at whether the next supported request receives data.

Educational software guidance. Trading involves risk. Read the financial and information disclaimers.

Step by step

1 Read whether the message says the service should be available on demand.
2 Open Help → Data Connections and compare the farm’s purpose with the data your app requests. Check whether any request is using that service.
3 Open the needed quote or chart during its available session and allow time for a response.
4 If the request fails, record that separate error and troubleshoot it rather than the idle notice.

A practical example

You have no chart-history request running, so a service goes idle. Later, you ask for a chart and it returns data. This is different from a request that times out or returns a permission error. Keep the idle notice in the log, but use the result of the real request to decide whether there is anything to fix.

Illustrative scenario, not a record of a trade placed during this review.

Screen reference

TWS Market Data Connections with farm purpose and status, plus API client columns — The observed services are connected and the API client list is empty. Use this panel to read current status; it does not reproduce a disconnect or prove an app handshake completed. Captured in TWS paper mode on 3 October 2026. Open the image for full size.

How to confirm the result The service should supply the requested data when it is needed and available to your account.

Mistake to avoid

Do not subscribe to extra data or alter API permissions solely because an idle service appears in a log.

Common questions

Is idle the same as disconnected?

No. Read the state description rather than treating all messages as failures.

What if data still does not arrive?

Check the request’s contract, data access, and returned error.

TWS error 200: contract not found or ambiguous TWS error 201: read the order rejection reason TWS error 202: why was the order cancelled? TWS delayed versus live data: how to tell

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.