Support Board
Date/Time: Thu, 04 Dec 2025 18:04:11 +0000
IBKR claims Deprecated TWS API version
View Count: 9
| [2025-12-04 16:55:18] |
| User113810 - Posts: 11 |
|
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 - 0 views 20251204_tws-exported-logs.txt - Attached On 2025-12-04 16:49:41 UTC - Size: 10.95 MB - 0 views |
To post a message in this thread, you need to log in with your Sierra Chart account: