Support Board

Date/Time: Mon, 29 Apr 2024 07:06:50 +0000

Post From: Trade filled by IB even though it was cancelled

[2013-12-19 18:50:13] Link To Thread - Link To Post [Go To First Post]
Sierra Chart Engineering - Posts: 104368
This is an example of the log messages you will see in the TWS log file when canceling an order: DD 07:41:48:159 JTS-EServerSocket-123: [0:62:68:1:0:0:0:INFO] Handling incoming CancelOrder message. DD 07:41:48:160 JTS-EServerSocket-123: [0:62:68:1:0:0:0:INFO] Cancelling orderId {107}. DD 07:41:48:160 JTS-EServerSocket-123: CANCELSOURCE SEL DD 07:41:48:160 JTS-EServerSocket-123: [0:62:68:1:0:0:0:INFO] OrderId {107} is cancelled. This is when the API logging level is set to "Info". We have also performed a code review, and see no problems at our side. Once the status of the order went to Pending Cancel, at that time the order cancellation was sent to TWS and there is no room for any kind of failure at that point in time. If you were not connected to TWS, you would not even be able to cancel the order to begin with. 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