Support Board
Date/Time: Fri, 29 Nov 2024 02:55:49 +0000
Post From: canceled stop order continues to have status SCT_OSC_OPEN
| [2023-03-17 11:58:09] |
| Berliner JFK - Posts: 45 |
|
Thank you @ondafringe, @Tony and @Sierra Chart Engineering. Here is what I know: 1. when I set the stop order variable explicitly to zero the problem is solved (see post # 15 above) 2. over a month of testing Sierra Chart's Simulation Mode(=on), Simulated Trading Service and Live Trading(Teton) I could not find evidence of a stop order housekeeping issue 3. over a day of testing persistence of standard variables in Sierra Chart/C++ with sample code, I could not recreate this issue. It only occurs in the context of my study function / trading system, which is automated and runs 100% unattended. This issue was solved by the explicit definition of the stop order variable (BEFORE: int stoporderID; AFTER: int stoporderID = 0;). Also, performing a manual refresh/recalculate (Insert) when it occurs, fixes it as well. I believe that this has to do with a special case of persistence possible in C++ @ondafringe. For now, I'm considering this solved, but hope that the root cause will become clear in the future. Thanks again @ondafringe, @Tony and @Sierra Chart Engineering! EDIT: I may do a deep-dive one day and add a ton of debug code to root cause this issue, because I'm not really satisfied with any of the explanations, but it's not a priority now. Date Time Of Last Edit: 2023-03-17 16:25:38
|