Support Board
Date/Time: Sat, 08 Aug 2026 21:26:25 +0000
Attached order (take-profit) cancel/replace rejected during partial parent fill
View Count: 272
| [2026-06-24 17:28:49] |
| PapaHertz - Posts: 5 |
|
I trade a bracket (Stop-Limit parent entry with attached Target and Stop) on NQU6.CME via Rithmic Direct. On fast entries that partially fill, the take-profit's quantity-increase modification is being rejected, and the result is that part of my position is left without a working profit target at the moment price reaches it. Two examples from my Trade Activity Log on 2026-06-24 (account LFE050-377U6HPS-TEST004): Internal Order 2479 (parent), ~15:47:07 UTC: parent partial-filled (1 then 2), TP child 2480 was sent at qty 1 and filled 1 at target, then the increase-to-3 modification on 2480 produced "Order modification failed — Order cancel/replace reject" at 15:47:07.969. Remaining contracts had no working TP and were stopped out. Internal Order 2482 (parent), ~16:41:43 UTC: parent partial-filled (1/1/2), the increase modifications on children 2483/2484 stacked ("Removed 1 prior delayed modification due to later modification… increasing 1 to 4"), then cancel/replace rejects, then at 16:44 "Order cancellation failed — timed-out waiting for cancel response." My questions: Is this the expected behavior when a parent fills in multiple parts faster than the attached-order quantity modifications can complete — i.e., the resize cancel/replace colliding with the child's own fill? "Reactivate Attached Order when Rejected Modification During Fill" is already set to Yes. It's firing in the log ("Reactivating order when performing delayed modification") but isn't preventing the exposure. Is there an additional setting or a configuration that more reliably handles partial-fill bracket resizing? Is there any way to have the attached orders submitted at full intended quantity rather than being resized incrementally as the parent partial-fills? Or is incremental resizing inherent to the feature? Would server-side bracket orders (Use Server Side Bracket Orders) change this behavior for Rithmic, or is Rithmic's OCO/bracket handling client-side here? Is there anything specific about Rithmic's cancel/replace handling during fills that makes this worse, versus other trading services? I have provided the full Trade Activity Log export and Trade Service Log for that session. |
| |
| [2026-06-26 12:33:18] |
| User229520 - Posts: 1 |
|
I am experiencing the exact same issue as described in this thread, and wanted to add my case as additional evidence that this is a recurring problem with Rithmic Direct DTC and bracket orders on partial fills. My setup: - Symbol: MNQU6.CME (Micro NQ) - Broker: Lucid (prop account) - Order routing: Rithmic Direct - DTC - Order type: Market parent with attached Target (Limit) and Stop, Client side bracket / Server side OCO - Entry quantity: 5 contracts What happens: When my Market parent order fills in two partial fills (e.g. 3 then 2 contracts), Sierra Chart immediately attempts to modify the Stop child order quantity from 3 to 5. Rithmic rejects this modification with 'Order modification failed | Rithmic Direct - DTC (Order cancel/replace reject)'. This rejection triggers a popup window (Trade Service Log) that opens on top of my chart at the exact moment of entry, blocking my view of the trade. From my Trade Activity Log (account LTE025-6JG32VR8-TEST001, 2026-06-25 UTC): - Internal Order ID 37741 (parent Market Buy x5), filled at 14:01:31 UTC in two partial fills - Internal Order ID 37743 (Stop child), modification from qty 3 to 5 rejected at 14:01:32.149 UTC - Stop filled at 14:01:36 UTC — only 5 seconds after entry - Same pattern repeated on Internal Order ID 37744/37746 at 14:02:55 UTC 'Reactivate Attached Order when Rejected Modification During Fill' is set to Yes in my settings. My questions: 1. Is there any Sierra Chart-side setting that would prevent the Trade Service Log popup from opening automatically when this rejection occurs, without disabling all error notifications? 2. Would disabling 'Adjust Attached Orders to Maintain Same Offset on Parent Fill' help avoid the rejection, and what would be the exact side effect on stop/target quantity management? 3. Is this rejection specific to Rithmic's handling of cancel/replace during fast fills, and is there any known workaround short of switching to Teton? I have the full Trade Activity Log export available if needed. Thank you |
Private File |
| [2026-06-26 21:56:12] |
| Sierra_Chart Engineering - Posts: 24431 |
|
This issue is strictly a Rithmic specific issue. We cannot help with this. If you want to use Rithmic, then we cannot help. We just simply cannot help with this at all. These are not Sierra Chart issues at all. 1. Is there any Sierra Chart-side setting that would prevent the Trade Service Log popup from opening automatically when this rejection occurs, without disabling all error notifications? General Settings Window: Never Automatically Open Message Log or Trade Service Log (Global Settings >> General Settings >> Log >> Log) 2. Would disabling 'Adjust Attached Orders to Maintain Same Offset on Parent Fill' help avoid the rejection, and what would be the exact side effect on stop/target quantity management? 3. Is this rejection specific to Rithmic's handling of cancel/replace during fast fills, and is there any known workaround short of switching to Teton? Would server-side bracket orders (Use Server Side Bracket Orders) change this behavior for Rithmic, or is Rithmic's OCO/bracket handling client-side here? Is there anything specific about Rithmic's cancel/replace handling during fills that makes this worse, versus other trading services? 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 Date Time Of Last Edit: 2026-06-29 20:13:57
|
To post a message in this thread, you need to log in with your Sierra Chart account:
