Login Page - Create Account

Support Board


Date/Time: Sun, 05 May 2024 03:45:21 +0000



Post From: Flatten and cancel

[2014-03-14 02:34:19]
Sierra Chart Engineering - Posts: 104368

What do you mean by "did not seem to generate an actual fill"? From what I can tell looking at earlier log entries (for example the above T4 stop trigger (8:18:14.000, 8:18:14.001, 8:18:14.003), it is normal for T4 order updates, on a stoploss, to first show as "Pending Open", then "Open", then finally "Filled". Order ID 797 is doing the same (goes from "Pending Open" to "Filled" at 9:09:18.002 and 9:09:18.003).
If these orders are not actually getting filled then this is either a bug in the version of Sierra Chart you are running or on the T4 side. We have confirmed that this does not occur in current Sierra Chart versions for stop orders that are not filled. Something like an order status being misreported, is considered a serious problem and it would be immediately resolved once detected.


The problem that I see is my "flatten and cancel" first happens. Sierra Chart sees that at 9:09:18.000 and 9:09:18.001 and logs "Cancelling all orders" (this works on ID 797) then "Auto-Trade: ....Flatten&Cancel" (this starts a new internal order ID 798). And then immediately afterwards, T4 stops me out at 9:09:18:003, while Sierra Chart continues working on the flatten and close (order ID 798) by submitting three T4 updates (market Buy 3). I'm sure T4 will concur after I show them the ServiceOrderID's for internal order ID 798 (I still need to check my official "fills" as you said).

We see no problem with orders 797 or 798 other than the status reporting with 797. 797 did not get filled because when we go to look at the Position Quantity it does not change. It only changes after the market order 798 fills and then goes flat. But we cannot see the fills because you do not select All Activity at the top left of the Trade Activity Log. We also see no reason why canceling of stop order suddenly causes it to become filled. It does not make sense.

And then immediately afterwards, T4 stops me out at 9:09:18:003,
If this order is really filling when being canceled, and it should not based upon its price, then you really have to ask CTS about this. After all of this, you really have everything in front of you. You have more information and an understanding of what is going on than we do. And if you are running the current version, you would not have the order status problem. This is one of the reasons why we use FIX connections.


The trouble we have seen with server-side OCO is straightforward. What we find is that when increasing the quantity or maybe decreasing the quantity of one of the orders in the OCO group, it does not always work. This is the only issue.

At this point, we cannot commit more time to this. These kinds of support requests are costly to us. If something is important, we will dedicate our time to it, no matter the cost. Otherwise we just have to draw the line on these kinds of requests and not get involved with them. They are very time-consuming.

This thread is closed and cannot respond more.
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: 2014-03-14 02:40:40