Home >> Support Board

Support Board

Date/Time: Mon, 10 Feb 2025 01:35:36 +0000

How to Post a Message for Support

Bid /Ask Quantity Triggered Stop (Main Trade Window)

View Count: 1987

[2018-02-18 00:31:28] #1 [Go To First Post]
Logan W - Posts: 28
The Bid / Ask Quantity Triggered stop from the main trade window does not seem to be working. (Tested on a DOM) I'm using this order type to market me out of the trade if the bid/ask quantity goes below a certain threshold where the stop is. However, when this occurs, the stop changes from a bid/ask quantity stop into a market order but does not place the trade. Instead, it allows price to go right through it without ever taking me out. Please advise.

[2018-02-18 01:05:27] #2 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We will look into this. 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

[2018-02-18 02:06:40] #3 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are surprised by this and we are unable to reproduce. For now we just need to let this go until the next release since perhaps there is something unknown changed that has resolved it. Do not use this order type for now. 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

[2018-02-18 03:23:46] #4 [Go To First Post]
Logan W - Posts: 28
I am using CQG data with local time-stamps. From reading other threads, I see others are having this exact same issue. Why on EARTH, would this not be a top priority?? This bug could destroy an account if this order type were to be used live. Date Time Of Last Edit: 2018-02-18 06:19:12

[2018-02-18 05:55:07] #5 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
From reading other threads, I see others are having this exact same issue. Actually no they are not. There case involves Attached Orders only. If that is what you are using, that is something that we misunderstood when you said "main trade window". Why on EARTH, would this not be a top priority?? This is a new order type, and we are doing our best. If we cannot reproduce, we cannot reproduce and it is that simple. The plan is to reevaluate once we get the new release out and users are able to test again since the problem may have already been solved. We have to handle things at our own pace and according to proper procedures. This bug could destroy an account if this order type were to be used live. This problem would not occur with live trading. That is clear. It is a simulated issue only. And also this is a new order type as well and we do put out a notice not to use it for live trading until it is proven in Trade Simulation Mode for you. And if you are really concerned about destroying your account, you should never never never under any circumstance use these types of orders. These are managed orders, and you would always be taking a chance for numerous reasons including the order not working as intended for reasons which are not in our control, or not working as you would like because it was not designed that way. We have yet to even put out the documentation for this order. Based on the way that you are communicating to us, we advise you to never use this order live under any conditions. So do not tell us about destroying your account. We take no responsibility for that whatsoever. This is common sense, and on top of that, we have put out on the What is New page to use these new order types in Trade Simulation Mode only until they are proven to you. Also, we were able to reproduce the problem as an Attached Order but not as the parent order. This issue only affects Trade Simulation Mode. 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: 2018-02-18 05:56:41

[2018-02-18 06:13:51] #6 [Go To First Post]
Logan W - Posts: 28
Thank you for your quick response. Yes, the issue occurs when using this order type as an Attached order. I understand that this is a new order type and you are still working out the kinks on your end. However, I very much hope that these order types that are available to us users are reliable enough to be used live. Volume stops have become a standard in most dom and charting packages. Thank you and I look forward to future updates. :) Date Time Of Last Edit: 2018-02-18 06:25:50

[2020-03-17 04:00:28] #7 [Go To First Post]
User745789 - Posts: 358
How to click on DOM column above/below the current inside price and place Bid Ask Quantity Triggered Stop order from the main Trade Window? This to open a position, not close, not part of a bracket order in Targets. I have right-click on DOM buy column to place a Buy Stop. How to I get that action to effect what ever style of Stop order is configured on the Trade Window Main interface?

[2020-08-18 11:15:50] #8 [Go To First Post]
User914757 - Posts: 8
I know this is an old thread, but I've observed this problem with BAQ stops in both Global Simulation Mode and just now the Trading Evaluator. When I went to check my auto-trading algo, I saw that Sierra Chart had become unresponsive just when the last bar was touching the stop. I had to force stop Sierra Chart. When I re-opened the application, price had gone through the stop as if it didn't exist. The stop was still there. This makes me ask two questions, 1) Does the Trading Evaluator support BAQ stops, and 2) Does the Trading Evaluator support OCO on the server, since even though my Sierra Chart hung, with Server-Side OCO, there should be no problem in triggering the stop anyway. Here's the chart image showing price has gone through the stop (short position). http://www.sierrachart.com/image.php?Image=1597749501346.png Date Time Of Last Edit: 2020-08-18 11:20:20

[2020-08-18 20:31:10] #9 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
I saw that Sierra Chart had become unresponsive just when the last bar was touching the stop. I had to force stop Sierra Chart. We need to understand this issue and get it resolved but it may already be resolved. Update to the latest version: Software Download: Fast Update Let us know if you still encounter this issue and we will look into it. We may need to do a remote assistance session with you. 1. These stops are not managed on the server. But within Sierra Chart. 2. Yes but it is not applicable in this case because this is a client-side held stop. 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

[2020-08-18 20:46:41] #10 [Go To First Post]
User914757 - Posts: 8
OK, I will upgrade and be monitoring it and let you know if ti happens again. Seeing that this type of stop is managed by SC on the client, and that SC had become unresponsive, I guess that's a highly probable cause for what happened. Thanks!

[2020-08-18 22:08:48] #11 [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We are suspecting that what you experienced is a deadlock condition. That issue is resolved. However, the circumstances which leads to that, are rare. So it probably is something else but we just have to see. 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

To post a message in this thread, you need to log in with your Sierra Chart account: