Check the complete parent-and-child order group. A filled entry does not prove both exits were accepted. Inspect each child’s ID, status, size, and any rejection before relying on the bracket.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Step by step
- 1 Find the entry order and identify its linked stop and target.
- 2 Check whether each child exists in the broker’s order view.
- 3 Read any child rejection and compare size, price increments, and supported order type.
- 4 Compare child activation with the parent’s filled size and state.
- 5 If protection is missing, resolve the specific missing exit through the supported workflow and check the final group.
A practical example
A bracket has an entry plus planned exits. If the entry fills and the stop is refused, the entry fill still exists. Look for each child by its own ID and read its result. Do not infer that the full group is healthy from the entry alone. Also check for an old target before you add a replacement group. A second set of exits can later close more than you intended.
Screen reference

Mistake to avoid
Common questions
Can the entry succeed while an exit fails?
Inspect each order separately; do not infer child acceptance from the parent.
Do TWS presets always create API brackets?
The client must use the supported mechanism. Verify what the app actually sends.