Support Board
Date/Time: Fri, 07 Feb 2025 12:41:56 +0000
Post From: Short Interruption with TT Routing 2020-05-27 / TT Account Balance/Credit Data
| [2020-05-28 08:48:25] |
| |
|
Ok this is what we have identified: Beyond the 2.5 minute interruption with connectivity to TT and we are waiting for response from TT on that, the remaining issue, was related to server-side bracket orders transmitted at that time. Since these are now required, we have identified a couple of minor issues related to these orders: 1. In the case of the Sierra Chart implementation of the DTC protocol both by the client and the server, when the client sends a server-side bracket order to the server and the server expressly rejects it, the children were getting rejected but the parent order was not. The parent order was just simply ignored. None of these orders were transmitted to the exchange. The side effect of this, is that a user would see the parent order left over from a rejected bracket order but this order was never sent to the exchange and was never actually working. It could have been easily cleared with this command: Trade Menu: Refresh Trade Data From Service (Trade menu) This is why we recommended just to reconnect to the data feed which effectively does the same thing. However, that order should have timed-out and in testing now we see that it is timing out. However, if the user kept trying to cancel it, it might not have. In any case there was never any harm done. This was never a working order. 2. The other problem was that Sierra Chart was not reconnecting to a backup server, if the server being connected to currently, rejects a new order, or an order modification or cancellation because it has no connection to the exchange server. This does work properly but was not working properly in the case of a rejected bracket order. This is now resolved. So this reconnect will happen. 3. Unrelated: There was never any inaccurate position reporting. That always remains accurate. If your broker was telling you something different about your positions, it was not accurate. The Sierra Chart order routing service, has consistently been reporting accurate positions with no known issue. ---- The items described above are not specific to the Sierra Chart order routing service, but apply in general, to order processing with the DTC protocol which would include LMAX, and also when using a sub instance of Sierra Chart. 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: 2020-05-28 19:13:04
|