Multi-Leg Partial Fill Recovery & Orphan Leg Neutralization

What your execution engine must do when Leg 1 of an Iron Condor fills and Leg 2 gets rejected by a price band. Within the Algorithmic Trading curriculum (Grid & Execution Engines → Smart Order Routing), this topic establishes the concrete quantitative rules and execution mechanics required for live market deployment.

Professional desks never rely on ambiguous visual guesses for partial fill. Instead, every entry, invalidation level, and risk parameter is defined mathematically before a single order reaches the exchange gateway.

Hover over key terms below for instant definitions: Partial Fill, Orphan Leg, and Multi-Leg Execution. For the complete mathematical derivation and edge-case analysis, open worked example & quantitative lookup matrix for partial fill recovery.

• Partial Fill — Core structural driver governing multi-leg partial fill recovery & orphan leg neutralization.
• Orphan Leg — Prevents premature entries and enforces mechanical discipline across Smart Order Routing.
• Multi-Leg Execution — Ensures worst-case scenario losses stay strictly within predetermined R-multiple budgets.

1. 1
   1. Pre-Session Calibration & Regime Check

   Measure baseline volatility and liquidity parameters for partial fill prior to market open.
2. 2
   2. Mechanical Signal Confirmation

   Wait for a completed bar close confirming the orphan leg threshold—never pre-empt mid-candle.
3. 3
   3. Risk-Normalized Sizing & Order Placement

   Compute exact lot quantity from the invalidation distance and dispatch via a Marketable Limit order.
4. 4
   4. Post-Trade Telemetry & Audit

   Log arrival price, fill slippage, and MAE/MFE metrics against the Smart Order Routing benchmark.

Implementation & Quantitative Model

1export function resolveMultiLegState(filledLegs: number, totalLegs: number, elapsedMs: number, timeoutMs = 3000) {2  if (filledLegs === totalLegs) return "COMPLETE";3  if (elapsedMs >= timeoutMs && filledLegs > 0) return "EMERGENCY_UNWIND_FILLED_LEGS";4  return "AWAITING_REMAINDER";5}

Cross-reference standard risk definitions such as drawdown, slippage, and Sharpe ratio when auditing your logs.