Support Board
Date/Time: Mon, 20 Apr 2026 14:16:29 +0000
IBKR claims Deprecated TWS API version
View Count: 1875
| [2026-01-15 13:11:41] |
| User293778 - Posts: 40 |
|
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. |
| [2026-01-15 19:17:01] |
| Sierra_Chart Engineering - Posts: 23562 |
|
Are you doing the trading for the symbol, where you want to see the position line on a chart, from within Sierra Chart? What you are referring to is Use Order Fill Calculated Position and either you are using Trade Window linking, or Trade Window Configurations where it is already set to be off and causing it to change: if I try to enable the “calculate position from order fills” setting it will revert back by itself to “no”.
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-15 19:17:26
|
| [2026-01-15 19:42:53] |
| User293778 - Posts: 40 |
|
Yes, orders were placed from Sierra. And yes, the problem could be the linking causing that setting to revert, although it shouldn’t be so because it is configured to change across all charts (3). I will check tomorrow or Monday, thanks for the hint. |
| [2026-02-06 23:51:39] |
| User113810 - Posts: 21 |
|
Evening This issue happened a couple of times over the last week I am in contact with IBKR again Will advise |
| [2026-03-10 13:27:38] |
| User113810 - Posts: 21 |
|
Morning I have been back and forth with IBKR. I will offer an attempted synopsis. IBKR is correct that the Contract object is returned via distinct callback functions IBKR is correct that the position data is present IBKR is correct that the logs show the data being delivered But: IBKR does NOT guarantee consistency across callbacks IBKR does NOT normalize contract fields IBKR does NOT provide a canonical symbol format IBKR does NOT guarantee the same fields are populated every time Sierra Chart’s integration layer is negatively impacted due to potentially fragile string parsing and call back reconciliation Sierra Chart relies on string matching instead of conId Sierra Chart discards updates when symbol mapping fails (?) Sierra Chart does not normalize IBKR’s inconsistent formats (?) So yes — Sierra Chart can be at fault, but only because IBKR’s API design forces them into a fragile position. 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: contract IDs instrument IDs GUIDs canonical contract objects The logs show inconsistent formats. Sierra does not like inconsistent formats. --------------------------------------------------------------------------------------------------- On the Sierra Support Board I have read Sierra expressed no interest in changing their internal architecture given IBKR is the apparently the only vendor that sends data in this manner. IBKR claims they pass information via callback function that will work. IBKR requests that I pass logs back to Sierra and "Suggest their technical team reach out to api@interactivebrokers.com if they need technical clarification from IBKR" From my perspective, given the random (and infrequent) nature of the issue, either Sierra or IBKR is NOT being consistent...agreed? And given the synopsis, seems like we will be at a standoff unless I change brokers. ------------------------------------------------------------------------------------------------------ What follows is the annotated (by IBKR) logs from a trading day WITH positions ERRORS and one WITHOUT. IBKR annotated message logs from trade date 20260217 (ERROR day) # The reqPositions function is called to subscribe to position updates. 07:59:41:139 (sync 07:59:40:281) <- [61;1;] # TRADE ID 35474 (FILLED, POSITION = 1) 09:40:28:577 (sync 09:40:28:121) <- [3;35474;;MNQ;FUT;202603;;;;CME ;;USD;;;;;BUY;1;LMT;24793.50;0 .0;DAY;;ACCT#REMOVED;;0;;1;;0;0;0 ;0;1;0;;;;;;;;;;0;;;3;;;0;;;0; 0;1.7976931348623157e+308;0;;;;;;0;;;;;;;;;;;;;;;;;; ;0;0;;;0;;0;0;0;0;;;;;;;;;;;;; ;;;;;;;;;;;20260217-14:40:28;] 09:40:28:923 (sync 09:40:28:467) -> [3;35474;Filled;1;0;24793.50;13 4978453;0;24793.50;0;;0] # TRADE ID 35475 (FILLED, POSITION = 2) 09:40:28:586 (sync 09:40:28:130) <- [3;35475;;MNQ;FUT;202603;;;;CME ;;USD;;;;;BUY;1;LMT;24793.50;0 .0;DAY;;ACCT#REMOVED;;0;;1;;0;0;0 ;0;1;0;;;;;;;;;;0;;;3;;;0;;;0; 0;1.7976931348623157e+308;0;;;;;;0;;;;;;;;;;;;;;;;;; ;0;0;;;0;;0;0;0;0;;;;;;;;;;;;; ;;;;;;;;;;;20260217-14:40:28;] 09:40:29:119 (sync 09:40:28:663) -> [3;35475;Filled;1;0;24793.50;13 4978454;0;24793.50;0;;0] # POSITION UPDATES RECEIVED - The position is shown as 1, and then 2, which is correct from observing the fills/executions above for two BUY orders 09:40:28:938 (sync 09:40:28:482) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;1;49587.62] 09:40:29:117 (sync 09:40:28:661) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;2;49587.31] 09:40:29:124 (sync 09:40:28:668) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;2;49587.619999999995] # TRADE ID 35476 (FILLED, POSITION = 1) 09:40:35:526 (sync 09:40:35:070) <- [3;35476;;MNQ;FUT;202603;;;;CME ;;USD;;;;;SELL;1;LMT;24809.25; 0.0;DAY;;ACCT#REMOVED;;0;;1;;0;0; 0;0;1;0;;;;;;;;;;0;;;3;;;0;;;0 ;0;1.7976931348623157e+308;0;;;;;;0;;;;;;;;;;;;;;;;;; ;0;0;;;0;;0;0;0;0;;;;;;;;;;;;; ;;;;;;;;;;;20260217-14:40:35;] 09:40:36:017 (sync 09:40:35:561) -> [3;35476;Filled;1;0;24809.25;13 4978455;0;24809.25;0;;0] # POSITION UPDATES RECEIVED - The position is shown as 1, which is correct 09:40:36:014 (sync 09:40:35:558) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;1;49587.619999999995] 09:40:36:023 (sync 09:40:35:567) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;1;49587.619999999995] 09:40:36:025 (sync 09:40:35:569) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;1;49587.619999999995] # TRADE ID 35479 (FILLED, POSITION = 0) 09:40:36:135 (sync 09:40:35:679) <- [3;35479;;MNQ;FUT;202603;;;;CME ;;USD;;;;;SELL;1;STP;0.0;24787 .50;DAY;;ACCT#REMOVED;;0;;1;;0;0; 0;0;1;0;;;;;;;;;;0;;;3;;;0;;;0 ;0;1.7976931348623157e+308;0;;;;;;0;;;;;;;;;;;;;;;;;; ;0;0;;;0;;0;0;0;0;;;;;;;;;;;;; ;;;;;;;;;;;20260217-14:40:36;] 09:40:46:508 (sync 09:40:46:052) -> [3;35479;Filled;1;0;24786.75;13 4978458;0;24786.75;0;;0] # POSITION UPDATES RECEIVED - The position is show as 0, which is correct 09:40:46:505 (sync 09:40:46:049) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;0;0.0] 09:40:46:511 (sync 09:40:46:055) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;0;0.0] 09:40:46:515 (sync 09:40:46:059) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;0;0.0] ---------------------------------------------------------------------------------------------------- IBKR annotated message logs from trade date 20260220 (NON-ERROR day) # TRADE 09:39:50:498 (sync 09:39:49:799) -> [3;35890;Filled;1;0;24835.00;34 6583279;0;24835.00;0;;0] # POSITION UPDATES RECEIVED (POSITION = 1 BECAUSE BUY) 09:39:50:503 (sync 09:39:49:804) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;1;49670.62] # TRADE 09:39:50:531 (sync 09:39:49:832) -> [3;35891;Filled;1;0;24836.25;34 6583280;0;24836.25;0;;0] # POSITION UPDATES RECEIVED (POSITION = 2 BECAUSE BUY) 09:39:50:535 (sync 09:39:49:836) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;2;49671.869999999995] # TRADE 09:40:00:098 (sync 09:39:59:399) -> [3;35892;Filled;1;0;24850.50;34 6583281;0;24850.50;0;;0] # POSITION UPDATES RECEIVED (POSITION = 1 BECAUSE SELL) 09:40:00:107 (sync 09:39:59:408) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;1;49671.869999999995] # TRADE 09:40:20:437 (sync 09:40:19:738) -> [3;35894;Filled;1;0;24866.75;34 6583283;0;24866.75;0;;0] # POSITION UPDATES RECEIVED (POSITION = 0 BECAUSE SELL) 09:40:20:448 (sync 09:40:19:749) -> [61;3;ACCT#REMOVED;750150193;MNQ;F UT;20260320;0.0;;2;;USD;MNQH6; MNQ;0;0.0] |
| [2026-03-10 14:57:28] |
| Sierra_Chart Engineering - Posts: 23562 |
|
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
|
| [2026-03-10 15:14:22] |
| User113810 - Posts: 21 |
|
Thanks for the fast feedback. I gave an email for the IBKR API team should you deem it worthy having a exchange directly with IBKR on this issue. I am out of my depth even though I did learn some things with the back and forth. I tried to stay with this issue as I am the one impacted. I don't think it is a good use of anyone's resources for me to remain in the middle and muddling communication. I have to live with this issue or switch brokers. |
To post a message in this thread, you need to log in with your Sierra Chart account: