Support Board
Date/Time: Sun, 08 Sep 2024 00:19:46 +0000
Unexpected behaviour using BE button in the Trade DOM
View Count: 234
[2023-08-18 13:51:50] |
DF52 - Posts: 19 |
Version 2532, trading evaluator with delayed CME data: in a long trade with attached orders which was moving toward the target limit order. On clicking the BE button, the attached stop order seemed to disappear rather than move to BE. I moved the target limit order to close out the trade. I have not been able to replicate this behaviour. I'm not skilled at reading logs but the stop order seemed to be cancelled rather than moved to BE. I don't have keyboard shortcuts or auto trading enabled. Any comments welcome. |
[2023-08-18 14:37:55] |
John - SC Support - Posts: 34254 |
Keep in mind that there is an offset that is set with the Move to Break Even. Refer to the following: Basic Trading and the Trade Window: Set >> Move to BE Offset So it's possible that this offset caused the Stop to move to a location off the visible prices for the chart. In the end, the way to know for sure what occurred is to look through the Trade Activity Log. You will need to filter for "Orders" for that symbol and find the information for what occurred when you selected the "Move to Break Even". There will be information on what occurred to the Stop order. Refer to the information at the following link for how to configure the filters at the top to get to the specific information you are looking for: Trade Activity Log: Viewing Historical Trade Activity For the most reliable, advanced, and zero cost futures order routing, use the Teton service: Sierra Chart Teton Futures Order Routing |
[2023-08-18 16:07:16] |
DF52 - Posts: 19 |
I think I worked out what happened. There is no BE offset, so the stop order moved to the entry price on clicking BE. In the DOM the stop order was then hidden behind the entry price information. I tried clicking on this line anyway to see if I could move the hidden stop order, and in doing so I clicked the hidden 'X' which cancels the order. Thanks for the suggestions. |
To post a message in this thread, you need to log in with your Sierra Chart account: