Support Board
Date/Time: Mon, 11 May 2026 18:14:24 +0000
[Locked] - Notice: Teton order routing lost connection at 3:50 AM 2026-03-18 US Eastern time
View Count: 310
| [2026-03-18 08:53:53] |
| Sierra_Chart Engineering - Posts: 23735 |
|
Early this morning at approximately 3:50 AM 2026-03-18. Teton order routing lost the connection to the exchange server for about two minutes. When this happens, due to the configuration of the CME ILink 3, which we have no control over, unfilled orders with a Time in Force of Day become canceled. Any child orders associated with those day orders will also be canceled. A parent order that has filled that has a working child and target, that have a Time in Force of good till canceled, which is the default, will not be canceled. Check your working orders and resubmit the orders that you need to. We have always questioned the concept of canceling orders on an iLink, when there is a lost connection. This has never made any sense to us but this is not something we have any control over . And actually we think that the exchange mandates this for iLink 3. We also looked into, why the connection was lost for so long, and made an adjustment. So if there is any underlying connectivity problem the connection will be restored, much more quickly. The extended time, related to a 30 second delay, which we had set many years ago for iLink 2, due to unstable behavior we would see when quickly reconnecting. We have now dropped this to 10 seconds (we probably could go lower on iLink 3). And the additional delay, was related, connecting to the backup server, and a second lost connection. There is always a redundant connection, available for Teton order routing, and why, there was not a failover to it, is related to operating system behavior. There really should not have been a lost connection due to that redundant connection which was up. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-03-18 14:26:02
|
| [2026-03-18 21:31:18] |
| Sierra_Chart Engineering - Posts: 23735 |
|
One clearing firm told us this: For your awareness, the FCM that provides the routing has the ability to disable the Cancel on Disconnect (COD) feature for CGW sessions. By default, CME enables COD when a CGW session is created; however, the clearing member handling the route can disable this feature at any time. MSGW sessions do not have this capability. This is good to know. We do recommend, that cancel on disconnect is disabled. We really do not see how it helps. Teton order routing has extensive redundancy. The more likely scenario, is a loss of Internet connectivity to the servers but they all have their own independent connectivity but the problem is there could be a fiber cut affecting the carriers we use. In which case using cancel on disconnect is of no value. Since the connection to the exchange would be up. And we are dropping the reconnect time down to 5 seconds. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2026-03-18 21:32:15
|
To post a message in this thread, you need to log in with your Sierra Chart account: