Why Binance Reduce-Only Orders Show 'Mismatch' Errors
A reduce-only order mismatch error typically occurs because the order direction is the same as the existing position direction, the order quantity exceeds the current closeable position size and fails the margin check. Additionally, if there is already a higher-priority reduce-only pending order in one-way position mode, a new order may be rejected due to priority competition.
The reduce-only order is designed to ensure only the reduction of an existing position, never to open a reverse position or increase the position. When the system detects that your order would violate this principle, it will be rejected outright.
Prerequisites
You have checked the "Reduce-Only" option in Binance Futures trading.
You hold a position in this contract, but the order is rejected or canceled by the system.
You can view your position and pending orders on the [Open Orders] and [Positions] pages.
Step 1: Check if Your Position Direction Matches the Order Direction
This is the most common reason for rejection.
Situation A: The order direction is the same as the existing open position direction
For example, you hold a 100-contract long position, but you place a buy reduce-only order. Buying to open long would increase the long position, which conflicts with the reduce-only principle of "only reducing positions".
Result: The order is rejected immediately. The system returns an error message like "ReduceOnly Order is rejected" or "Order direction is the same as the open position direction."
Completion criteria: Go to the [Positions] page, confirm your position direction, and ensure the reduce-only order direction is opposite (i.e., use sell to close a long position, buy to close a short position).
Situation B: Order direction is opposite, but order quantity exceeds closeable position size
For example, you hold a 100-contract long position, but you place a sell reduce-only order with a quantity of 150 contracts. The first 100 contracts sold would close the position, but the remaining 50 contracts would become a new short position.
Result: The order is rejected. Because the part exceeding the position is a "new open," violating the reduce-only principle and failing the margin check.
Completion criteria: Check your order quantity to ensure it is less than or equal to your current position size.
Step 2: Check for Higher-Priority Reduce-Only Pending Orders
During the queuing of reduce-only orders, a higher-priority limit order will cause orders with lower priority to be canceled.
Priority rule: A reduce-only limit order with a more aggressive price (closer to the market price) and larger quantity has higher priority.
Example: Assume you hold a 100-contract long position in one-way mode:
You have a reduce-only limit sell order at 1,000 USDT for 50 contracts (Order A).
Then you place another reduce-only limit sell order at 999 USDT for 60 contracts (Order B).
Because Order B's price is more aggressive and its quantity exceeds the remaining closeable quantity of the position, Order A will be automatically canceled by the system.
Completion criteria: Check all reduce-only pending orders for this symbol in [Open Orders]. If there are multiple, the system will keep the one with the highest priority and cancel others. You only need to keep the one that best fits your strategy.
Step 3: Try Using a Market Reduce-Only Order as a Fallback
If you see the error "Reduce-Only Order Failed. Please cancel existing pending orders and retry," Binance recommends trying a market reduce-only order.
Why it works: Market reduce-only orders (and stop-market reduce-only orders) have the highest priority and are not subject to the limit order queue rules above.
Completion criteria: If limit orders are frequently rejected, consider switching to a market order to close the position, which can execute the reduction faster.
Common Failure Reasons
Misconception: Thinking a reduce-only order can "incidentally" open a reverse position
The most fundamental misunderstanding is that a reduce-only order is never a reverse opening instruction. The system strictly checks if the order would increase your position. If you understand "reduce-only" means "only closing, never opening," you'll avoid most mismatch errors.
Risk Warnings
Position mode conflict risk: If your USDⓈ-M and COIN-M futures have different position modes (e.g., one-way vs. hedge mode), all reduce-only orders (including stop orders) may be canceled when the system synchronizes modes. It is recommended to regularly check that position modes are consistent.
API limitations: If you use API trading, note that Binance's algo order API (/fapi/v1/algoOrder) does not support the reduceOnly parameter. To close a position, use closePosition: true with no quantity set; otherwise, you'll get error -1106.
System delays in extreme market conditions: During extreme market conditions, system pressure may cause order processing delays, and many reduce-only orders may be rejected or not executed, leading to failed risk management.
How to Confirm the Operation Is Complete
Cancel or adjust your reduce-only order, then resubmit an order with a quantity equal to or less than your current position and in the opposite direction. Check the order status:
If the order status is "Pending" or "Filled," the issue is resolved.
If the order is still rejected, check the error code. If it's -4118 or -2022, it still indicates a reduce-only logic conflict; further adjust order parameters or refer to Step 3 to use a market order.
