Support Board
Date/Time: Wed, 05 Feb 2025 09:59:37 +0000
Scaling Out of Position does not change stop quantity
View Count: 914
| [2020-03-10 04:23:47] |
| jaxscott - Posts: 57 |
|
This is new behavior that has never happened before version 2057. Having scaled into a multiple contract long (or short, doesn't matter) position, scaling out of the position sells (or buys) contracts as expected, but an attached stoploss order does NOT change. For example, scaling into a 10 contract position changes the quantities accordingly to all attached orders. Selling those 10 contracts, scaling out, reduces back down the position, but the stop loss attached order REMAINS at 10. Which, as you can surmise, can cause a huge freaking problem, technically speaking. This is behavior never seen before and is new to this version. Yes, I have Support Scale in/out checked as they have always been. |
| [2020-03-10 04:48:57] |
| |
|
We just tested this in the UAT environment using server-side bracket orders with the Sierra Chart order routing service and did not observe a problem. Scaling out of a +10 position, through sell orders, reduced the quantity of the attached orders. There is some other explanation your case. Also nothing has changed with this functionality. We recommend performing tests in Sierra Chart Trade Simulation Mode to verify the functionality. 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-03-10 04:49:26
|
| [2020-03-10 06:22:42] |
| jaxscott - Posts: 57 |
|
This is done in simulation mode.
|
| [2020-03-10 06:36:20] |
| |
|
We are able to reproduce this when the Target order is manually canceled and there is only a remaining Stop Attached Order. We are looking into the reason why this is the case and we will implement a solution.
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-03-10 06:57:01] |
| jaxscott - Posts: 57 |
|
Yes, this is exactly the situation that I was executing.
|
| [2020-03-10 07:29:24] |
| |
|
We see the reason for this but this is nothing new. It definitely is not new behavior at all. It has always been this way.
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-03-10 14:46:58] |
| jaxscott - Posts: 57 |
|
Regardless, it's a problem and it's great that you're implementing a solution. Thx.
|
| [2020-03-10 18:27:57] |
| |
|
Yes a solution will be out in the next release.
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-03-10 18:28:02
|
To post a message in this thread, you need to log in with your Sierra Chart account: