Support Board
Date/Time: Mon, 11 May 2026 11:08:39 +0000
Flatten execution delay
View Count: 204
| [2026-03-25 21:06:34] |
| User358827 - Posts: 24 |
|
Hi - I am getting a delay when I click my flatten button of 2 to 3 seconds once it is clicked. I have copied my trade log below so you can see the executions times. I am running the trading DOM as a sub instance with no other charts running in the sub instance. I have cleared all recent and current bid/ask volume, chart interval update set to 50, remote buffer delay set to 75 and max depth level set to 50. It seems to be losing time on the confirmation of the cancelling as shown below. Flatten action settings set to flatten and cancel. Any help on this would be appreciated. Trade Log with times: Initiating: ESM26_FUT_CME #32 | Canceling non-market orders during Flatten 07:53.3 ESM26_FUT_CME #32 | Canceling non-market orders during Flatten 07:53.3 ESM26_FUT_CME #32 | Canceling non-market orders during Flatten 07:53.3 ESM26_FUT_CME #32 | User order entry. Flatten&CancelAllOrders | Last: 6607.75. Current Position quantity: 1 | AO=1 07:53.3 Order update (New). Info: Order from DTC client #7. Sierra Chart. 127.0.0.1 | Client text: Tag: SDRegSimpleStop.twconfig. Text: Tag: SDRegSimpleStop.twconfig 07:53.3 Order update (Canceled). Info: Teton CME Routing (Canceled). Info: CME (Canceled). SecurityID=42140864. Operator=S5SC514. Text: Attached order. Parent: 12289. Tag: Attached order. Parent: 65294. Tag: SDRegSimpleStop.twconfig. Text: Attached order. Parent: 65294. Tag: SDRegSimpleStop.twconfig 07:55.9 Order update (Canceled). Info: Teton CME Routing (Canceled). Info: CME (Canceled). SecurityID=42140864. Operator=S5SC514. Text: Attached order. Parent: 12289. Tag: Attached order. Parent: 65294. Tag: SDRegSimpleStop.twconfig. Text: Attached order. Parent: 65294. Tag: SDRegSimpleStop.twconfig 07:55.9 Order update (Order update). Info: Teton CME Routing (Order update). Info: CME (New). SecurityID=42140864. Operator=S5SC514. Text: Tag: Tag: SDRegSimpleStop.twconfig. Text: Tag: SDRegSimpleStop.twconfig 07:55.9 Order update (Filled). Info: Teton CME Routing (Filled). Info: CME (Trade). SecurityID=42140864. Operator=S5SC514. Text: Tag: Tag: SDRegSimpleStop.twconfig. Text: Tag: SDRegSimpleStop.twconfig 07:55.9 Updated Internal Position Quantity to 0. Previous: 1. Fill of InternalOrderID: 65297 07:55.9 Order update (Filled). Info: Teton CME Routing (Filled). Info: CME (Trade). SecurityID=42140864. Operator=S5SC514. Text: Tag: Tag: SDRegSimpleStop.twconfig. Text: Tag: SDRegSimpleStop.twconfig 07:55.9 |
| [2026-03-25 22:03:52] |
| Sierra_Chart Engineering - Posts: 23735 |
|
So you have order confirmations enabled? Not sure what we are supposed to tell from the log above. It does not have information that is useful. There are no timestamps. 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-25 22:30:36
|
| [2026-03-25 23:13:00] |
| User358827 - Posts: 24 |
|
No i don't have order confirmations enabled. I will send over my trade activity log file with the timestamps. I am experiencing about a 2 to 3 second delay between when I press the flatten button and when i get flattened. The delay looks like in the log is happening waiting on the response from Teton for cancelling.
|
Attachment Deleted. Private File |
| [2026-03-30 06:10:51] |
| Sierra_Chart Engineering - Posts: 23735 |
|
We have started to look into this and wanted to check the timing on the server but could not because we do not know the trade account and the clearing firm. But we did check, some of the processing at around that general time on the server and it remains very fast and as expected. The order processing is very fast with an order going to the exchange and getting a response all under .5 ms. Ultimately we do not know where the delay is occurring. We just simply do not know. There could be a lot of causes. There could be delayed processing on your system. There could be some high processing load in Sierra Chart causing a problem. There could be network connectivity issues causing a problem. We really do not know. One thing is certain, is there is no indication a problem on the server. So therefore this issue is somewhere else. And where we do not know. We have no control over anything else. We would recommend going through a process of elimination like using a different Internet connection. Trading from the main instance of Sierra Chart. Opening just one chart and trading from that. 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-30 14:39:23
|
| [2026-03-30 18:36:41] |
| User358827 - Posts: 24 |
|
Thanks for getting back to me. I was investigating this most of last week and the cause seems to be the interaction between the sub instance (the trading dom) and the main instance(the charts). The charts seemed to be causing a delay before the order could get sent to Teton. I worked with my tech person at Stage 5 trading so that now have the trading dom going to Teton and not passing through the sub instance to main channel. This has been working great. Thanks for getting back to me. I think this issue is now resolved.
|
To post a message in this thread, you need to log in with your Sierra Chart account: