Support Board
Date/Time: Mon, 19 Jan 2026 05:21:16 +0000
IBKR claims Deprecated TWS API version
View Count: 1145
| [2025-12-04 16:55:18] |
| User113810 - Posts: 17 |
|
I am on SC verison 2813 64-bit Issue: Positions not flowing back to Sierra Over last two months this happened randomly (often for a whole day) and typically corrected next day. I contacted IBKR and they pointed back to Sierra. In past instances, the bracket orders I would use in relation to the postions executed from Sierra via IBKR would still work. Trade Activity logs would eventually catch up. Today, 20251204, the issues escalated in a bad way. The stops and take profits did not work. This makes complete sense IF Sierra does NOT know the position (no acknowledgement). The execution activity did not show in the regular Postion and Trade Orders windows. I could find no trace of the orders at all. I later tested orders outside of market and I could see pending and cancelled states as normal. I then executed again to create fresh logs and watched the Take profit NOT execute. My Trade Activity log remains empty for the day. Yesterday activity is still there (as a check). Full disclosure: I used Grok to try and help frame the rest of this request as I am weak at this stuff. Sorry if this is annoying. Trying to make it less painful for you Subject: IBKR Reports Deprecated TWS API (v10.19/Server 176) in Sierra Chart Diagnostics – Request Confirmation on Compatibility I'm experiencing intermittent order acknowledgments and position updates when trading futures via IBKR TWS integration (e.g., fills execute in TWS but delay or do not show in Sierra's Trade Activity Log, DOM, Charts). I attached diagnostics analysis logs as suggested by IBKR. (20251204_tws-exported-logs.txt and 20251204_api-exported-logs.txt) IBKR support also related the following: "Sierra Charts is using a deprecated (non-functional) TWS API package... Server version is 176 (API 10.19). Our minimum is 10.37 (server 203)." Per your documentation (according to GROK) (Interactive Brokers Trading Service page), Sierra uses a direct socket connection without external DLLs, with superb integration and ongoing TWS adaptations (e.g., recent position request fixes in What's New). Help Topic 76 notes avoiding IBKR's API components to prevent threading issues.Sierra Chart version: [e.g., 2674] TWS/IB Gateway version: [e.g., 10.30] Socket port: 7497 (live) Settings: Download Historical Order Fills on Connect = Yes; Instance Client ID = 0 Message Log excerpts: [Paste 2-3 relevant lines, e.g., "Trading server did not acknowledge new order" with timestamps] Affected symbols: MNQZ5 Is this a known IBKR misdiagnosis of Sierra's custom implementation? Any recommended TWS config (e.g., API logging level) or Sierra update to align with IBKR's 10.37 minimum? Anything else I need to provide? Thank you for your expertise. I love your software even if I don't have expertise in these areas. Your support boards and docs have been invaluable so far. |
 20251204_api-exported-logs.txt - Attached On 2025-12-04 16:49:35 UTC - Size: 89.83 KB - 31 views 20251204_tws-exported-logs.txt - Attached On 2025-12-04 16:49:41 UTC - Size: 10.95 MB - 37 views |
| [2025-12-04 19:03:31] |
| John - SC Support - Posts: 44021 |
|
You have this statement: "Sierra Charts is using a deprecated (non-functional) TWS API package... Server version is 176 (API 10.19). Our minimum is 10.37 (server 203)."
Is that statement from Grok or from Interactive Brokers? -- Are these orders being created in Sierra Chart or are they being done outside of Sierra Chart? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-12-04 19:05:42] |
| User113810 - Posts: 17 |
|
From Interactive Brokers chat support All orders originating from Sierra Chart Until this issue arose I had no reason to interact with IBKR TWS for orders/positions except to check if working/accurate Date Time Of Last Edit: 2025-12-04 19:08:18
|
| [2025-12-04 20:02:12] |
| John - SC Support - Posts: 44021 |
|
If you have not restarted Sierra Chart since you had the issues you mention, then please get us your Trade Service Log by following these instructions: Support Board Posting Information: Providing Lines From Trade Service Log For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-12-04 20:14:29] |
| Sierra_Chart Engineering - Posts: 22436 |
|
This does not make sense to us because it is TWS which is providing the server: "Sierra Charts is using a deprecated (non-functional) TWS API package... Server version is 176 (API 10.19). Our minimum is 10.37 (server 203)."
So we are not controlling the server. It is what you have installed. Maybe you just need to update TWS. The TWS API package is what you provide, and is part of TWS. We have no control over that. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-04 20:14:47
|
| [2025-12-04 20:18:28] |
| User113810 - Posts: 17 |
|
I believe I did restart Sierra Chart to check if version update would fix issues That said, pretty confident I traded once after that check and the issue at hand was not resolved File attached as requested Looks like I did restart Sierra Chart after the first position and trade issue Also looks like I traded THREE times since that re-open and the issue persisted I looked for a unique value in the Message Log near the start and found Program Path C:\SierraChart2\ with DateStamp 20251204 09.41.45.393 When I checked a MessageLog for a different version of Sierra Chart, the path was again unqiue and near the start with a prior day time stamp Date Time Of Last Edit: 2025-12-04 20:42:52
|
Private File Private File |
| [2025-12-04 21:09:32] |
| John - SC Support - Posts: 44021 |
|
There are all kinds of errors showing up from Interactive Brokers. The most important is from the Trade Service Log where we see the following: Trading message from IB: Order Canceled - reason:. Error Code: 202. ServiceOrderID: 31295. InternalOrderID: 35970.
But this does not tell us anything. You would need to ask Interactive Brokers what this error is about. -- There is also the following: Trading message from IB: Order Event Warning:Attribute 'Outside Regular Trading Hours' is ignored based on the order type and destination. PlaceOrder is now being processed. Error Code: 2109. ServiceOrderID: 31293. InternalOrderID: 35963.
We remember a discussion in this Support Board regarding this, although we never got a real answer as to where "Outside Regular Trading Hours" is coming from. Refer to the following: Ineractive Brokers - Overnight trades not filling In this case, we recommend looking at your "Time in Force" settings. There are two places for this, one for the parent and one for attached orders. Check both of these and make sure they are set to either "Day" or "Good Till Cancelled", as these are the only ones we know that should work. But you can check with Interactive Brokers regarding the other options. They may be able to give you some insight as to what "Outside Regular Trading Hours" is about as well. Refer to the following: Basic Trading and the Trade Window: Main >> TimeInForce (Time in Force): Attached Orders: Time In Force -- In your Message Log you have the following: Message from IB: Market data farm connection is OK:usfarm.nj. IB Error Code: 2104. Request ID: -1.
We really do not know whether this is an issue or not. If you are not setup to get any data from Interactive Brokers, then this could just be the normal situation. -- With regards to these messages in the log: 2025-12-04 09:41:50.447 | Interactive Brokers | Sending client version: v100..176 +PACEAPI. Waiting for acceptance.
2025-12-04 09:41:50.450 | Interactive Brokers | TWS server version: 176 2025-12-04 09:41:50.450 | Interactive Brokers | TWS time: 20251204 09:41:49 EST As stated previously, make sure you have a current version of the TWS software. Do not do a Beta version, just the most recent stable release. -- And finally, with regards to this: Program path: C:\SierraChart2\
Normally it really does not matter much, as this is just the location of your Sierra Chart software. But, with the issues you are having, we have to wonder if you have multiple copies of Sierra Chart and you may have an issue with multiple connections to the same TWS software? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-04 21:10:12
|
| [2025-12-04 21:30:53] |
| User113810 - Posts: 17 |
|
Evening Yet another example of Interactive Brokers wasting my time and your time I updated my TWS API to Stable Version 10.37 I did a test order and it worked as expected For completeness, I will follow up here if that changes or remains, in fact, Stable The API Stable Version alledgedly updates about 1x per year The Latest Version can be "every couple of weeks" Fun times given I went to IBKR 3x this year suggesting something is wrong with their API and they never suggested checking the version. My bad, I suppose, for not Googling how to check my version and determine which version works best with Sierra To be clear, I put this all on IBKR. Maybe somewhere in your Support Threads someone encountered this already but I did not find it. Perhaps this Version information "solution" or "check" can be added to your page if new. Thanks again for your timely assistance |
| [2025-12-04 21:37:33] |
| User113810 - Posts: 17 |
|
The Outside regular trading hours" log line is annoying to flash by all the time. And the order code issue I will follow up on. As for program Paths I have my main version of SC for busy charts and is SC data SC2 is just for trades, charts are clean, and is connected to IBKR with "Allow Support for Sierra Chart Data Feeds" enabled Partly screen organization, partly preference |
| [2025-12-04 22:17:44] |
| John - SC Support - Posts: 44021 |
|
In the end, we have had issues both ways. Update to their latest release, and it breaks compatibility. Stay on an older version and it breaks compatibility. So all we can do is react based on what is occurring at the moment.
For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-12-05 18:13:22] |
| User584084 - Posts: 317 |
|
I am running SC Version 2717 and IB TWS Version 10.35. I only trade futures so I am not having any issues with sending orders to IB TWS. IB sent out an email Oct 20th about the need to update to IB TWS Version 10.37 because of changes to IB TWS because of LotSize Configuration. Not sure if this has anything to do with your issue but posting it as an FYI. See below: Interactive Brokers Urgent: Notice of Change to TWS API LotSize Configuration Dear Client, IBKR strives to constantly improve software security and performance, as well as ensure continued compliance with regulatory changes. As a result, we adjust on a regular basis the technical requirements and configuration needed to use our platforms and, in this case, TWS API. Due to an external SEC rule update (RIN 3235-AN23), we are required to enforce a change in the round lot sizes of US stock that will vary by price from November 3, 2025. To remove disruption to your trading operations, you must upgrade at a minimum to TWS and TWS API to 10.37 Stable or newer. If you are already using version 10.37 or above, you may have to ensure that you have ticked the setting “Send market data in lots for US stocks for dual-mode API clients.” This will ensure you remain informed of the true bid/ask/last sizes. Please consider this when managing your risk and use a supported configuration. Regards, Interactive Brokers Date Time Of Last Edit: 2025-12-05 19:53:15
|
| [2025-12-05 21:46:14] |
| User113810 - Posts: 17 |
|
Evening all 20251205 upddate: Sierra/TWS worked correctly today for position display and order management As for questions from John SC Support about Message logs: -Trading message from IB: Order Canceled - reason:. Error Code: 202. ServiceOrderID: 31295. InternalOrderID: 35970. This was likely a race condition where I attempted to place a Stop-limit order for Entry and the market was away from that price at arrival. Human error. You can also get this error if: Order price is too far away from current market price, and order was manually cancelled by the user or an OCO function, avoidance of self trading, some other order parameter was invalid -Trading message from IB: Order Event Warning:Attribute 'Outside Regular Trading Hours' is ignored based on the order type and destination. PlaceOrder is now being processed. Error Code: 2109. ServiceOrderID: 31293. InternalOrderID: 35963. Little was gained for feedback from IBKR support. I gave them logs from today and yesterday and they just kept repeating that the CME hours in the system are 0930-1600 EST and 1800-1700 EST. DAY orders will cancel at 1700 EST. I would note that today's message log had no instances of this message. So perhaps the change in API version cleaned this up. -Message from IB: Market data farm connection is OK:usfarm.nj. IB Error Code: 2104. Request ID: -1. Response was "normal situation as API pings for connections the user is not employing. Weird answer but I moved on. |
| [2026-01-13 18:39:32] |
| User293778 - Posts: 37 |
|
Good afternoon, Sierra doesn't display Interactive Brokers positions anywhere, neither on the charts nor on the Trade Positions Window; in the latter only the symbol names and position size are shown but their avg entry prices and all the other fields display zero, regardless of whether they are old positions or positions entered from Sierra. Pending ordes are on the other hand correctly displayed, on both the charts and the Trading Orders Window. I have subscribed to the Denali Nasdaq Totalview and the Consolidated Tape data feeds, read all the docs, modified my Symbol Settings to have the automatic substitution for the IB symbol names and that works because I can enter orders, but there is no way I can get the position display working. I don't know if the reason for this could be the new IB API as claimed in previous posts or maybe I could be missing something but I would ask you guys to take a look, please. Thanks. |
| [2026-01-13 19:01:35] |
| John - SC Support - Posts: 44021 |
|
Just so we understand. You are entering an order from Sierra Chart, and that order is properly getting to Interactive Brokers, as you can see the order on the Interactive Brokers software (or through the website, or some other method other than Sierra Chart)? But, you are then not seeing the orders on the Sierra Chart software? After you do a trade and you have this situation, please get us your Trade Service Log by following these instructions: Support Board Posting Information: Providing Lines From Trade Service Log For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-13 19:28:58] |
| User293778 - Posts: 37 |
|
Thanks for the prompt answer! If I understand you correctly, it’s not exactly so. I can see the pending orders both on Sierra and on TWS, the orders will be filled normally and If I activate “Show Order Fills” (ctrl+shift+o) on my charts they will be correctly displayed with their markers. But once filled what I can’t see are my position lines, their size and entry prices. So, if one of my orders gets filled while I am not looking, there is no way to know that I have a position on, unless “show order fills” is active (in this case only because of its little marker). On the Trade Positions Windows all my existing positions display always zero as avg price, old positions as well as those entered from Sierra. To summarize, orders work but positions don’t. Thanks! |
| [2026-01-13 19:39:30] |
| User293778 - Posts: 37 |
|
I forgot to mention that my Trade Accounts Monutor/Balances Window doesn’t display anything, not even the account number, although it appears and can be used as a possible filter. There is nothing to filter, of course.
|
| [2026-01-13 19:54:25] |
| John - SC Support - Posts: 44021 |
|
Once the order is filled, do you have working orders as well (Target and/or Stop)? Are these showing on the chart? Also, once the order is filled, are you able to verify that the position actually exists through another means? We still want to see the Trade Service Log after one of these situations occurs so we can see if there is anything in that log. Follow these instructions: Support Board Posting Information: Providing Lines From Trade Service Log For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-13 20:21:20] |
| User293778 - Posts: 37 |
|
Q1: if I have bracket orders active those will be correctly placed and displayed, both in Sierra as in TWS. Q2: once the order is filled I see that the position exists by looking into TWS, but in Sierra I have no way of knowing it. Q3: I will get back to you with the log tomorrow, as I am no longer in front of the computer. Thank you very much for your attention! |
| [2026-01-14 17:20:44] |
| User293778 - Posts: 37 |
|
Hi again, Continuing from yesterday, I have opened Sierra and made a test trade on the ticker RKLB_MBO mapped to RKLB-STK-SMART-USD. The order has filled and the bracket orders have been correctly placed but still no position display in Sierra, neither on the charts nor in the Trade Positions Window, although the position does exist in TWS. Previous to this trade I placed an order but canceled it right after to enable first the Bracket Orders, given your interest in that. I have also noticed that if I try to enable "use order fill calculated trade position data" in chart settings, the option will automatically reset itself to No after 5 seconds or so. Thanks! Here all the lines from today's Trade Service Log after making the above mentioned trade: 2026-01-14 17:34:17.163 | Interactive Brokers | Received Open orders end message. 2026-01-14 17:34:17.410 | Interactive Brokers | Requesting Open orders. 2026-01-14 17:34:17.410 | Interactive Brokers | Sent reqAutoOpenOrders request 2026-01-14 17:34:17.826 | Interactive Brokers | Received Open orders end message. 2026-01-14 17:34:22.602 | Denali Data Feed (Market Orders Data) | MaxConnectionsDifferentDevices = 1, NumCurrentConnectionsDifferentDevices = 1 2026-01-14 17:34:22.602 | Denali Data Feed (Market Orders Data) | MaxConnectionsForSameDevice = 3, NumCurrentConnectionsForSameDevice = 1 2026-01-14 17:39:52.760 | TradeActivity files query time: 0.079966 seconds. Entries: 3. BeginDateTimeUTC: 2025-01-07 05:00:00.000. Outstanding queries: 1 2026-01-14 17:39:52.767 | TradeActivity files query time: 0.006651 seconds. Entries: 3. BeginDateTimeUTC: 2025-01-06 05:00:00.000. Outstanding queries: 0 2026-01-14 17:39:54.090 | TradeActivity files query time: 0.008336 seconds. Entries: 3. BeginDateTimeUTC: 2025-01-06 05:00:00.000. Outstanding queries: 0 2026-01-14 17:40:36.964 | Trading message from IB: Order Canceled - reason:. Error Code: 202. ServiceOrderID: 13101. InternalOrderID: 10088. 2026-01-14 17:40:39.807 | Trading message from IB: Order Event Warning:Attribute 'Outside Regular Trading Hours' is ignored based on the order type and destination. PlaceOrder is now being processed. Error Code: 2109. ServiceOrderID: 13104. InternalOrderID: 10091. 2026-01-14 17:41:12.375 | Interactive Brokers | Requesting Open orders. 2026-01-14 17:41:12.375 | Interactive Brokers | Sent reqAutoOpenOrders request 2026-01-14 17:41:12.381 | Interactive Brokers | Received Open orders end message. 2026-01-14 17:42:32.214 | Trading message from IB: Order Canceled - reason:. Error Code: 202. ServiceOrderID: -652. InternalOrderID: 10019. I paste here also the first lines of the message log after login: 2026-01-14 17:34:16.347 | External Service | Interactive Brokers | Connecting to 127.0.0.1:7496 2026-01-14 17:34:16.347 | Network | IB TWS socket (3) | Creating socket. 2026-01-14 17:34:16.347 | Network | IB TWS socket (3) | New receive buffer size: 5242880 2026-01-14 17:34:16.347 | Network | IB TWS socket (3) | Connecting to IP: 127.0.0.1. 2026-01-14 17:34:16.856 | External Service | Interactive Brokers | Sending API sign: API 2026-01-14 17:34:16.856 | External Service | Interactive Brokers | Sending client version: v100..176 +PACEAPI. Waiting for acceptance. 2026-01-14 17:34:16.882 | External Service | Interactive Brokers | TWS server version: 176 2026-01-14 17:34:16.882 | External Service | Interactive Brokers | TWS time: 20260114 17:34:17 Central European Standard Time 2026-01-14 17:34:17.141 | External Service | Interactive Brokers | Connected. Sending Start API command. 2026-01-14 17:34:17.141 | External Service | Interactive Brokers | Waiting for account information. 2026-01-14 17:34:17.163 | Unset | IB Account information received. 2026-01-14 17:34:17.163 | External Service | Interactive Brokers | Received 1 Trade Accounts from TWS. 2026-01-14 17:34:17.163 | External Service | Interactive Brokers | Connected to Live account. 2026-01-14 17:34:17.163 | External Service | Interactive Brokers | Trade Account: U7039. Index: 0 2026-01-14 17:34:17.163 | Unset | Updated verified funded futures trading account ending date to: 2026-02-13 16:34:17 2026-01-14 17:34:17.163 | External Service | Interactive Brokers | Connection to server complete. 2026-01-14 17:34:17.163 | Historical Data | No download requests in the queue to start downloads for. | Number times message added: 3 2026-01-14 17:34:17.163 | Unset | Updated verified funded futures trading account ending date to: 2026-02-13 16:34:17 2026-01-14 17:34:17.169 | External Service | Interactive Brokers | Next valid order ID: 13100 | Number times message added: 1 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:hfarm. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:eufarmnj. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:cashfarm. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:usfuture. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:jfarm. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:usfarm.nj. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:eufarm. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:usfarm. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Market data farm connection is OK:usopt. IB Error Code: 2104. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: HMDS data farm connection is OK:euhmds. IB Error Code: 2106. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: HMDS data farm connection is OK:cashhmds. IB Error Code: 2106. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: HMDS data farm connection is OK:fundfarm. IB Error Code: 2106. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: HMDS data farm connection is OK:ushmds. IB Error Code: 2106. Request ID: -1. 2026-01-14 17:34:17.169 | Unset | Message from IB: Sec-def data farm connection is OK:secdefil. IB Error Code: 2158. Request ID: -1. 2026-01-14 17:34:17.170 | External Service | Interactive Brokers | Next valid order ID: 13100 2026-01-14 17:34:17.205 | Unset | Mapping AAPL_MBO to AAPL_MBO. Service code: us_equities_with_depth.data 2026-01-14 17:34:17.205 | Unset | Using symbol data fast lookup vector 2026-01-14 17:34:17.205 | External Service | Denali Data Feed | Starting real-time market data updates for: AAPL_MBO (AAPL_MBO). ID: 1 Service code: us_equities_with_depth.data 2026-01-14 17:34:17.205 | External Service | Denali Data Feed | Connecting to the server ds33.sierracharts.com. Port 10046 2026-01-14 17:34:17.205 | External Service | Denali Data Feed | Requesting security definition data for: AAPL_MBO (AAPL_MBO). ID: 1 2026-01-14 17:34:17.205 | External Service | Interactive Brokers | Starting real-time market data updates for: AAPL-STK-SMART-USD. ID: 2 2026-01-14 17:34:17.205 | External Service | Interactive Brokers | Subscribing to Symbol: AAPL, SecurityType: STK, Expiration: , Exchange: SMART, Primary Exchange: , Currency: USD, Multiplier: , CallPut: , Strike: , LocalSymbol: , TradingClass: 2026-01-14 17:34:17.205 | External Service | Interactive Brokers | Requesting security definition data for: AAPL-STK-SMART-USD. ID: 2 2026-01-14 17:34:17.205 | Historical Data | Added historical Intraday data request for AAPL_MBO to the queue. 2026-01-14 17:34:17.205 | Unset | Intraday data recording state for symbol AAPL_MBO is set to download 'Pending'. 2026-01-14 17:34:17.205 | Historical Data | Triggering next historical data download in queue. 2026-01-14 17:34:17.207 | Historical Data | Delaying start of download for AAPL_MBO. 2026-01-14 17:34:17.285 | Network | DTC Client socket (4) | Creating socket. 2026-01-14 17:34:17.285 | Network | DTC Client socket (4) | New receive buffer size: 5242880 2026-01-14 17:34:17.285 | Network | DTC Client socket (4) | Connecting to IP: 69.39.70.245. 2026-01-14 17:34:17.363 | External Service | Interactive Brokers | Starting real-time market data updates for: RKLB-STK-SMART-USD. ID: 3 2026-01-14 17:34:17.363 | External Service | Interactive Brokers | Subscribing to Symbol: RKLB, SecurityType: STK, Expiration: , Exchange: SMART, Primary Exchange: , Currency: USD, Multiplier: , CallPut: , Strike: , LocalSymbol: , TradingClass: |
| [2026-01-14 17:59:43] |
| John - SC Support - Posts: 44021 |
|
We see the following 2 lines in your Trade Service Log: 2026-01-14 17:40:36.964 | Trading message from IB: Order Canceled - reason:. Error Code: 202. ServiceOrderID: 13101. InternalOrderID: 10088.
2026-01-14 17:42:32.214 | Trading message from IB: Order Canceled - reason:. Error Code: 202. ServiceOrderID: -652. InternalOrderID: 10019. We can not relate directly to which orders these are for, but they are fairly explicit in that Interactive Brokers is reporting back to Sierra Chart that an order has been canceled. It looks like Sierra Chart is properly "not dipslaying" the Position information, as IB has reported that the order was canceled, so no position was ever opened. What we can not answer, is why IB would report it "canceled" and then still have it open in their system and in the market. We wish we could help further, but you would need to talk to IB about this. Specifically, check to see if "InternalOrderID: 10019" is your parent order. They should be able to track that down for you. For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-01-14 18:00:02
|
| [2026-01-14 18:31:07] |
| User293778 - Posts: 37 |
|
Ok, thanks. But Sierra detects that the order was filled because it shows its marker when activating order fills on the chart. In any case, that doesn't explain why all positions on the Trade Positions Window are zero as per the attached partial screenshot or why the Trade Accounts Monitor/Balances Window shows nothing. Thank you very much anyway, I understand that IB must be difficult. |
Private File Attachment Deleted. |
| [2026-01-14 18:34:53] |
| Sierra_Chart Engineering - Posts: 22436 |
|
Sierra Chart does not support account balance data from Interactive Brokers anymore: or why the Trade Accounts Monitor/Balances Window shows nothing.
Sierra Chart does not support the position average price from Interactive Brokers: why all positions on the Trade Positions Window are zero
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-01-14 18:35:35
|
| [2026-01-14 19:20:07] |
| User293778 - Posts: 37 |
|
I don’t recall having read anything about this. It would’ve been good to know this beforehand. Ok, then if positions are not displayed and balances are not shown, I can’t really find any real use case for Sierra with Interactive Brokers. Sierra is absolutely the best program for futures, no doubt, but for stocks I find it falls very short. Thanks for your attention. |
| [2026-01-14 22:45:36] |
| Sierra_Chart Engineering - Posts: 22436 |
|
Even though you do not see the Position Average Price in the Trade Positions window, you will see it within the charts you are trading from: Trading Information Windows: How Average Price for Positions Is Calculated and Used It is calculated from the order fills. This will be accurate. If you need help with that, let us know. And regarding the account balances, you can see those within TWS. Do you need this information within Sierra Chart? We will find the information on our What is New page and the related support board thread about the changes. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2026-01-15 13:11:41] |
| User293778 - Posts: 37 |
|
Hi, As I mentioned before the position line doesn’t appear on the charts or the dom. I wish it did but it doesn’t. And as I mentioned in post #19, if I try to enable the “calculate position from order fills” setting it will revert back by itself to “no”. So, if I have a position on there is no indication on the charts or dom that there is a position open on the instrument and the NPL on the charts will always display zero, not the live NPL. Only after closing the position it will display the correct closed NPL. The order fill markers and connecting lines will be indeed correctly displayed. It is pretty strange. |
To post a message in this thread, you need to log in with your Sierra Chart account: