Support Board
Date/Time: Sat, 25 Jul 2026 19:23:16 +0000
ACSIL sc.CancelOrder() on Attached Target OCO Sibling-Linked-Order Cancellation Behavior
View Count: 25
| [2026-07-25 16:58:22] |
| Userneshkito - Posts: 4 |
|
In Sierra Chart version/build using SC_DLL_VERSION 2900, when an ACSIL study calls sc.CancelOrder() on an individual working attached Target order belonging to OCO Group 1, with a separate per-group Stop order as its sibling and multiple OCO groups in the original bracket: 1. Is the sibling Stop canceled, left working unchanged, or quantity-adjusted? 2. Can the cancellation propagate to linked split parent orders or another OCO group? 3. Is the behavior different for: a) Sierra Chart Internal Trade Simulation, b) Sierra-managed client-side brackets, c) Teton/Sierra intermediary-server brackets, d) third-party server-side bracket orders? 4. Which statement in the Attached Orders documentation governs explicit cancellation through sc.CancelOrder(): - “When one fills or is canceled, the other will be canceled,” or - “The other order in the OCO Group (sibling) will not be canceled either”? Please provide the exact behavior for explicit ACSIL cancellation, not fill-triggered OCO handling. |
| [2026-07-25 17:01:24] |
| User431178 - Posts: 895 |
|
Docs: Automated Trading From an Advanced Custom Study: sc.CancelOrder When an order is canceled, all other working orders that are linked to the order you are canceling, will also be canceled. Orders may be linked when the order is part of an order set that contains an Attached Order with an OCO Group setting of All OCO Groups and there was more than one OCO Group used. You can see if an order is part of a linked group by looking at the Link ID field in Trade >> Trade Orders Window for the order. Orders that share the same Link ID are linked. |
| [2026-07-25 17:45:04] |
| Userneshkito - Posts: 4 |
|
Thank you. We understand that cancellation propagates to other working orders only when they are linked through a shared nonzero Link ID. We need clarification on one specific case: An attached Target order and its Stop order are OCO siblings, but both have Link ID = 0. If ACSIL explicitly calls sc.CancelOrder() on the working Target order, will Sierra Chart also cancel its attached OCO sibling Stop order? In other words, does explicit cancellation of one attached OCO order cancel its sibling independently of the Link ID, or does the sibling remain working when both Link IDs are 0? Please answer specifically: Target canceled → Stop remains working; or Target canceled → OCO sibling Stop is also canceled. This concerns explicit cancellation through sc.CancelOrder(), not a Target fill. |
To post a message in this thread, you need to log in with your Sierra Chart account: