Support Board
Date/Time: Mon, 25 Nov 2024 10:38:40 +0000
Is scale in / scale out client or server managed?
View Count: 577
[2024-02-29 13:00:58] |
User601931 - Posts: 11 |
Is scale in / scale out client or server managed? I'd like to understand where the scale in/out is managed in the event of a lost connection & the impact on my position. Example: Setup scenario: I have scale out turned on. I have a long position of 5 and attached OCO target and stop orders 20 points away (total exit Q = 5) I enter an order to sell 1 lot 10 points away. If the market moves up in the next 10 mins... I expect 1 lot to be filled at 10pts and 4 lots to be filled at 20 pts since scale out will automatically reduce the target exit quantity. My final position is flat. However, what happens if I loose my network connection for 30 mins and the market has moved up significantly? When I log back in, what will I see? If scale in/out is server managed, I should be flat. If the scale in/out is client managed, I will be overfilled & short 1 since the client was offline and target Q not adjusted. Can you advise on the behavior? thanks. |
[2024-02-29 17:17:13] |
John - SC Support - Posts: 36238 |
Scale In/Scale Out is not specifically server managed or not. These settings affect the attached orders for your position. So what matters is whether your trading service supports server side managed OCO or Bracket orders. It looks like you are using the Teton Order Routing service, in which case OCO and Bracket orders are server managed (except for Market if Touched). So when you Scale In/Out, the information is stored on a server separate from your local system. Refer to the following: Sierra Chart Teton Futures Order Routing: What is Included For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
[2024-03-01 11:21:57] |
User601931 - Posts: 11 |
Thanks for your reply. I'd like to just confirm my understanding of your reply: If I understand your reply: In my scenario above, if the scale in/out is stored separate from the local, this means the server is monitoring the exit total Q against my position Q and will automatically reduce the target quantity total by -1 once the "sell 1 @ 10pt away" is filled. Therefore, when I reconnect, my position will be flat and not overfilled by -1. Is that correct? I'm just trying to make sure I understand because at the time I loose connection, I have a total order exit quantity of 6, not 5. Thanks. |
[2024-03-01 16:00:40] |
John - SC Support - Posts: 36238 |
Do not think of it as the "Scale In/Scale Out" is stored on the server. What is stored on the server is the Target and Stop. When you Scale In/Scale Out the quantity of those Targets and Stops (on the server) are adjusted based on your Scale In/Scale Out settings. -- I'm just trying to make sure I understand because at the time I loose connection, I have a total order exit quantity of 6, not 5.
We are not understanding the above statement. Are you saying that you have seen a specific issue? For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
[2024-03-02 16:15:25] |
User601931 - Posts: 11 |
Do not think of it as the "Scale In/Scale Out" is stored on the server. What is stored on the server is the Target and Stop. When you Scale In/Scale Out the quantity of those Targets and Stops (on the server) are adjusted based on your Scale In/Scale Out settings. Got that. But is the client sending the instruction to the server to adjust the Q, or it is server managed? Because if the client is dead, it can't tell the server to change the Target/Stop quantities. If you have resting exit orders to scale out, then there is a risk of overfill. See my example below. We are not understanding the above statement. Are you saying that you have seen a specific issue? Yes, always in sierra charts. Please try the following: Assume the market is trading at 4000, and 1 tick = 0001. 1. Submit a market buy, Q = 5, with attached orders. The target is 20 ticks offset and the stop is 20 ticks offset. 2. In the order book & position. You should have: -> a long position of Q = 5 at price = 4000. -> one sell limit order at 4020, Q =5. Call this "Order A" -> one sell stop order at 3080, Q = 5. Call this "Order B" 3. Assume the market moves up slightly and you want to exit 1 lot at 4010 (ie: scale out) 4. Place a sell order for: Sell Q = 1, Limit, Price = 4010. Call this "Order C" 5. In the order book & position, Sierra charts will show: -> position: long, Q = 5, price = 4000. -> Order A: one sell limit order at 4020, Q =5 -> Order B: one sell stop order at 3080, Q = 5 -> Order C: one sell limit order at 4010, Q = 1 6. Sum up of the sell limit order quantities = 6. Therefore, if I loose the network/power and my local SC instance dies, I have 2 exit limit orders sitting on the server, with a total Q = 6, which is greater than my position quantity of 5. From my observation, Sierra Charts only adjusts the target/stops quantity on change in POSITION, not when you submit a new exit order (ie: order to scale out). So a disconnect can mean overfill rather than flatten because the server Q never got adjusted. Unless the adjustment is server managed, or I am missing a setting to force a recalculation of the resting target/stop attached orders based on sum of all exit order quantities (by ordertype). Thanks. |
[2024-03-02 19:37:21] |
Sierra_Chart Engineering - Posts: 17172 |
There is no server management of these options. They are client-side only.
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 |
[2024-03-03 13:13:45] |
User601931 - Posts: 11 |
thanks for clarifying. If possible, I'd like to request an additional option to trigger the recalculation of the attached stop/target quantities when a new exit order is submitted, rather than just on position update when scaling out. This would be more 'fail-safe' in the event of a client disconnect. I'm specifically asking this since I am living in a semi-rural area and have had problems with periodic disconnects or power outages. I switched to the teaton routing to make my trading more fail safe (ie: stronger server bracket order management), however using the scale out/in options poses some risk since the server is holding an overcount of order quantity. thanks. |
[2024-03-06 01:07:47] |
Sierra_Chart Engineering - Posts: 17172 |
We will look at adding an option for 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 |
[2024-03-09 01:03:31] |
Sierra_Chart Engineering - Posts: 17172 |
There will be an option for this in the next release in Global Settings >> Global Trade Settings >> Scale In/Out.
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 |
To post a message in this thread, you need to log in with your Sierra Chart account: