Support Board

Date/Time: Sat, 04 May 2024 22:59:33 +0000

Post From: Flatten and cancel

[2014-03-14 02:04:44] Link To Thread - Link To Post [Go To First Post]
User35525 - Posts: 180
It looks like Sierra Chart needs to watch for broker-initiated action messages -- like "CTS T4 order update. T4 status: Stop Trigger" -- and then intelligently handle any SC-initiated orders that may have been submitted a few milliseconds BEFORE the broker-initiated order. If the idea is to "get flat", and SC is "managing" that for us, then the final outcome should be flat, just as if a human was trading, and saw that they needed to take additional action to really get flat. So to recap, right now with 997, if SC said "get flat" at nearly the same time as the server-side stop is triggered, there can be a "collision". Maybe the collision doesn't happen if the broker first initiates the stop (SC can just watch for that easily), but it can and does happen when SC initiates the stop immediately before the broker. This all gets pretty complex, but it looks like something that SC should be able to handle. I'm not trying to so HFT programming, but just would like to see SC play well with a server-side OCO and "flatten and cancel" command. Will upgrade to 1102 this weekend. Best Regards, Ted Date Time Of Last Edit: 2014-03-14 02:05:51