Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 13 May 2024 19:00:50 +0000
Post From: SC via Interactive Brokers not correctly setting OCO orders - important!
| [2015-05-02 20:48:04] |
| |
|
Now we understand what is going on in this most recently reported case. Originally, Sierra Chart would never modify a server-side bracket order set after it is initially sent, unless the user were to manually modify one of the orders or a trailing stop order needs to be adjusted. At some point, based upon a user request, we were asked to maintain the same offset for the Attached orders that they originally had to the parent order. This happens if Global Settings >> General Trade Settings >> Adjust Attached Orders to Maintain Same Offset on Parent Fill. So Sierra Chart will modify the Attached Order prices and use the existing quantity of those orders when sending the order modification to TWS. Before the order modification Interactive Brokers indicated the order quantity of the orders is 1: Order 14:09.0 CL-201506-NYMEX IB open order update 18819 498 Limit 1 Buy 58.12 Open Close 18818 Order 14:09.0 CL-201506-NYMEX IB open order update 18820 499 Stop 1 Buy 58.72 Open Close 18818 Possibly because there was a partial order fill of the parent before? We cannot see that from the Trade Activity Log because you are not showing the fills, only the order updates. You need to select All Activity. When the bracket order server-side managed, this will no longer apply in the next release: Global Settings >> General Trade Settings >> Adjust Attached Orders to Maintain Same Offset on Parent Fill. This is a good example of the consequence of us being too accommodating to user requests. After having said all of this, we did indicate in post #18 above, that if Sierra Chart is modifying those orders, you will see the order going to Pending Modify state. So as we said, you do have the information in front of you as to exactly what is happening. Also, this does reveal that even a trailing stop order can lead to this problem. So when you are using server side bracket orders, you cannot use trailing stops because that can trigger the problem as well. So we do acknowledge, that what we said above previously that once the bracket order set is sent, Sierra Chart will not modify those orders unless the user modifies them or a trailing stop order modifies them, is not correct if the option described above, is enabled. However, it is not that Sierra Chart had made any mistake with the quantity, it is just simply a complex interaction which occurs which has no solution other than the fact that a client connected to TWS really cannot modify bracket orders, without running the possibility of a scenario like this occurring under some conditions. 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, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2015-05-03 00:32:06
|