Support Board
Date/Time: Wed, 10 Dec 2025 20:46:03 +0000
Alerts/Notification with targets and stops
View Count: 201
| [2025-02-27 03:08:27] |
| User925540 - Posts: 115 |
|
Is this a bug? General Trade Settings > Notifications > Play Alert When Order Filled > set to Sound#1 General Trade Settings > Notifications > Play Alert When Target Filled > set to Sound#2 General Trade Settings > Notifications > Play Alert When Stop Filled > set to Sound#3 In Twconfig > Targets: Target: MIT Client >>> When Filled, Sound#1 is fired (expected Sound#2). Stop: Stop Limit Client >>> When filled, Sound#2 is fired (expected Sound#3). |
| [2025-02-27 06:33:57] |
| Sierra_Chart Engineering - Posts: 21777 |
|
We do not know what the exact issue is in your case and we are not going to be allocating any time to this. We are 100% certain there is no problem at all with those alerts and we are certain of that. We do not know what the situation is in your case. There is no way we would be able to reproduce any problem like 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, use the Teton service: Sierra Chart Teton Futures Order Routing |
| [2025-02-27 14:51:39] |
| User925540 - Posts: 115 |
|
I can reproduce this easily with a fresh installation of the latest build (2743). There is no my case or another case, it's a simple test that takes a minute to reproduce, not sure how you can be "100% certain there is no problem" when it is that easily reproducible. Seems to me that "target" is only considered a target if it's a limit order, and "stop" is considered a stop if it's not a limit order. |
| [2025-03-02 21:34:52] |
| User925540 - Posts: 115 |
|
Can someone sensible from Sierrachart support please look into this just to confirm if this is a bug or a misconfiguration? Steps to reproduce the issue: 1) Install latest build (2744). 2) >> Global Settings >> General Settings >> Alerts >> Set any alert sound from the built in files for Alert#1 #2 and #3 3) >> Global Settings >> General Trade Settings > Notifications > Play Alert When Order Filled > set to Alert#1 >> Global Settings >> General Trade Settings > Notifications > Play Alert When Target Filled > set to Alert#2 >> Global Settings >> General Trade Settings > Notifications > Play Alert When Stop Filled > set to Alert#3 4) >>Trade Window >> Targets Target order type: MIT Client Stop order type: Stop Limit Client 5) Let Target (MIT - Client) fill, sound notification of Alert#1 is triggered. Let Stop (Stop Limit - Client) fill, sound notification of Alert#2 is triggered. |
| [2025-03-03 07:14:26] |
| Sierra_Chart Engineering - Posts: 21777 |
|
OK thank you. We will look this over. We were not giving consideration to the nonstandard order types. We would have only tested with standard order types. There may be a problem there that we do not recognize. 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: 2025-03-03 07:14:38
|
| [2025-03-03 07:25:20] |
| Sierra_Chart Engineering - Posts: 21777 |
|
The behavior you see is correct. The market if touched client becomes a Market order. And the client side stop order becomes a limit order. It is all 100% correct. We will not be spending any further time on this. This is just how it is and the behavior is 100% correct. If you choose to use client-side orders, these are going to have their issues. So in the end we were proven right. 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: 2025-03-03 07:25:40
|
| [2025-03-03 10:45:13] |
| User925540 - Posts: 115 |
|
Thank you for looking into this. Logically, one would think that the notification is based on the order category (Target vs Stop) and not the order type (Market vs Limit) because there are market targets and limit stops. But that is just my understanding/logic that I would (gladly) be Ok to be corrected! |
| [2025-03-23 15:03:29] |
| User925540 - Posts: 115 |
|
Following up on this .. can you please explain, even if it's a client side order, why is the notification based on the order type (Market vs Limit) and not based on the order category (Target vs Stop)? I want to start using ntfy and I cannot do so because I'll be receiving wrong notifications. The normal behavior should be "Target Filled" notification triggered when the target of a bracket order is reached - regardless if the order was client/server or limit/market. Same thing with "Stop Filled" notification, it should be triggered regardless of what it was client/server or limit/market. Notification based on order category (Target/Stop - as the notification name implies), please, not order type. |
| [2025-03-24 08:20:47] |
| Sierra_Chart Engineering - Posts: 21777 |
|
We will not be spending further time on 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-03-24 08:20:55
|
| [2025-12-10 10:06:04] |
| User925540 - Posts: 115 |
|
Hi, any chance someone from the SC with a bit more patience look into this and explain why this cannot be fixed (if at all)? The notifications should not be based on the order type (Market / Limit) but instead on whether the order is a target or a stop. It doesn't make the product unusable, but getting a notification that the target is being hit when it is actually the stop is imho a defect. |
To post a message in this thread, you need to log in with your Sierra Chart account: