Support Board
Date/Time: Mon, 20 Apr 2026 12:27:18 +0000
Post From: IBKR claims Deprecated TWS API version
| [2026-03-10 14:57:28] |
| Sierra_Chart Engineering - Posts: 23549 |
|
Sierra Chart’s integration layer is negatively impacted due to potentially fragile string parsing and call back reconciliation We do not understand this.Sierra Chart relies on string matching instead of conId Sierra Chart discards updates when symbol mapping fails (?) No this is not the case.The suggestion was that Sierra Chart’s internal string matching architecture predates IBKR's API and uses canonical, stable symbol strings and was not designed to use: We do not know what is meant by "internal string matching architecture". contract IDs instrument IDs GUIDs canonical contract objects This also makes no sense: predates IBKR's API The interface to TWS could not predate it because there was nothing that we could have even done before the TWS API even existed.There is some support for the contract ID. It is used when requesting the security definition data or the contract data. When receiving a position update, the given contract ID is used to request the security definition data using that contract ID. We do not understand any of the given log messages. They are all out of context and not being looked at during actual debugging and do not mean anything to us. 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-03-10 15:01:35
|