What Matters
A reduce-only rejection can mean the order would increase exposure, targets the wrong position, exceeds the live quantity or conflicts with other closing orders. Removing the flag changes what the order is allowed to do. First reconcile the position, account mode, order size and outstanding exits. Reduce-only constrains exposure; it does not guarantee execution, a price or protection from liquidation.
DN Evidence Block
Last verified: 29 October 2026. Scope: Bybit’s reduce-only and position-mode help pages and V5 order documentation; OKX’s basic order-types guide; Binance Futures’ failed-order guide. Original DN tool: seven-check exit audit, state worksheet and synthetic reversal example.
Finding: the same closing intention can behave differently across position modes, existing orders and product rules. Bybit describes rejecting reduce-only orders when no position exists. OKX describes modifying or canceling competing reduce-only orders according to priority. [1] [3]
Limits: documentation review only. DN did not submit live orders, test fills or compare venue reliability. The 2027 edition uses evidence reviewed in October 2026. Account-specific instructions, contract rules and current API specifications govern actual orders.
1. Confirm there is still a position to reduce
Check the live position in the correct account and contract. A take-profit, stop, manual close or another strategy may already have reduced or closed it. The position visible when you prepared the order can differ from the position when the venue evaluates it.
Bybit’s reduce-only guide says a new reduce-only order is rejected if no open position exists. It also describes size adjustments or cancellation where quantity exceeds the position or conflicts with other active orders. [1] A rejection can therefore show a safeguard working rather than a broken close button.
Record: position size, direction, account/subaccount, instrument and snapshot time. If there is no position, investigate why it closed before attempting another trade.
2. Check one-way versus hedge mode and the intended leg
In a one-way system, an opposite-side order can offset an existing net position. In a hedge-mode system, a trader may hold long and short legs separately. Opening the opposite leg is not necessarily the same operation as closing the original one.
Bybit’s position-mode guide specifically requires direction and Open/Close intent in hedge mode. Its one-way example explains how an oversized opposite-side order without reduce-only can close a position and open exposure in the other direction. [2]
Record: account mode, long/short leg and the action the venue will interpret. Do not change mode as a blind troubleshooting step. The effects and prerequisites are product-specific.
3. Use the current quantity and the correct unit
Check whether the size field expects contracts, base-asset units or another unit. A dollar value on the position screen is not automatically the quantity that belongs in an order field. Contract multipliers and linear versus inverse specifications matter.
A partial exit changes the amount left to close. An order copied from an earlier position snapshot can become oversized. Some interfaces may trim quantity; others may reject it, and different API modes can have different rules. Avoid relying on a universal auto-trim behavior.
Record: requested quantity, live position quantity, unit, multiplier if relevant, minimum size and quantity step. Match these to the exact interface or endpoint rather than another venue’s example.
4. Inventory other closing orders and their priority
Review active limit exits, conditional orders and position-level TP/SL. Multiple exits may compete for the same remaining position. A newly accepted order can also change which older orders remain valid.
OKX’s order-types guide describes automatic modifications and cancellations based on position size and order priority. It also notes that reduce-only and ordinary orders can coexist. [3] Binance Futures lists competition between reduce-only orders among the reasons for rejection or cancellation. [4]
Record: each exit’s ID, size, price, trigger, status and instruction. Do not cancel all exits automatically: doing so can remove protection while the position remains open. After any deliberate change, inspect the remaining protection again.
5. Separate reduce-only from the rest of the order instructions
Reduce-only concerns exposure direction. A limit price concerns execution price; post-only concerns maker execution; time-in-force concerns how long an order can remain or whether partial fills are allowed. A conditional trigger concerns when an order becomes eligible to enter its next execution stage. These settings answer different questions.
Bybit’s API documentation describes post-only cancellation when an order would immediately fill, and market-order handling with slippage protection that can leave an order unexecuted when suitable liquidity is unavailable. [5] An exit can have the right exposure instruction and still fail an execution condition.
Record: the exact error code and message, order type, time-in-force, trigger basis and price protection. Do not label every rejected exit a reduce-only problem.
6. Reconcile any earlier attempt before resubmitting
If the previous attempt timed out or its state is unclear, treat it as unresolved until you inspect order history, fills and the current position. A rejection and a missing acknowledgement are different events.
Use DN’s Order Timeout Guide to reconcile the original request. An accepted request does not establish a fill, and a cancellation cannot undo quantity that has already executed.
Record: original client and venue IDs, cumulative fills, remaining live quantity and final cancellation state where applicable. Preserve one coherent record of the attempted exit.
7. Verify the resulting position and remaining safeguards
After changing an order, confirm what the exchange actually accepted, amended, canceled or executed. Then inspect the resulting position and all remaining exits. Do not infer full closure from a success banner alone.
For an API integration, validate the request against current product documentation and confirm state through the venue’s supported order/fill channels. Bybit’s order-create documentation says its acknowledgement is asynchronous and directs users to WebSocket confirmation. [5] This does not establish identical semantics for every venue.
Record: final filled quantity, residual position, active protection and unresolved discrepancies. If records remain inconsistent, use official support with identifiers and timestamps, excluding secrets.
DN Close-Order Audit Worksheet
Copy this manual tool into your notes. Mark every row verified, mismatch or unknown. An unknown is a question to resolve, not a pass. The worksheet does not connect to your account or execute orders.
| Check | Evidence | Status |
|---|---|---|
| Live position | Account, contract, size, direction, timestamp | ________ |
| Mode and leg | One-way / hedge; intended close action | ________ |
| Quantity | Requested size, correct units, current rules | ________ |
| Competing exits | Order IDs, quantities, prices and states | ________ |
| Execution settings | Type, trigger, time-in-force, error code | ________ |
| Earlier attempts | Fill and cancellation reconciliation | ________ |
| Result | Residual exposure and active safeguards | ________ |
DN decision rule: first identify the cause of the rejection. If you change an instruction, explicitly reassess what that revised order may open, close or leave unprotected. There is no universal replacement order suitable for every account.
Worked example: removing the flag can reverse a trade
Synthetic one-way-mode example, not a live platform test. A trader originally held a 1 BTC long position. A separate exit has already sold 0.6 BTC, leaving 0.4 BTC long. The trader then attempts a 1 BTC close order based on the stale size.
| Stage | Illustrative quantity | Interpretation |
|---|---|---|
| Original long | +1.0 BTC | Earlier position |
| Already sold | −0.6 BTC | Confirmed partial exit |
| Remaining long | +0.4 BTC | Current position to reconcile |
| New unrestricted sell, if fully filled | −1.0 BTC | Assumes sufficient margin and venue acceptance |
| Resulting net position | −0.6 BTC | New short exposure |
The arithmetic is 1.0 − 0.6 − 1.0 = −0.6 BTC. At a hypothetical $100,000 per BTC, that final short has $60,000 absolute notional. This is not a loss calculation and excludes fees, price movement and contract multipliers. Actual acceptance, execution and reduce-only treatment depend on the product.
A correctly applied reduce-only constraint is intended to prevent that reversal. Whether the oversized instruction is rejected, resized, canceled or partly executed must be established from the specific rules and returned state. The example is a reason to refresh quantity, not a recommendation to place any particular exit.
What reduce-only does not promise
It does not guarantee liquidity, execution before liquidation, a particular price or uninterrupted exchange access. It also does not guarantee that reducing one leg of a multi-leg hedge reduces total portfolio risk. Closing a hedge can increase net directional exposure elsewhere. Review the full position structure if the trade is part of a hedge.
For those separate questions, see the DN Stop-Loss Reliability Test and Hedge Break Index.
Before choosing your next trading venue
Use DN Pathfinder to compare your requirements, then verify current order controls, account eligibility and exact product rules. Moving venue does not resolve an existing rejected order. For migration economics, use the Venue Switching Cost Calculator.
Disclosure: linked DN tools and reviews may contain affiliate links. These optional research pathways are not execution or recovery services. No signup is required to use the audit.
Methodology, limits and corrections
DN reviewed five official documents and separated exposure constraints from mode, quantity, order competition and execution rules. The audit and example are original editorial tools, not a venue ranking or tested reliability score. Documentation is evidence of stated behavior, not proof of performance in stressed markets. Version 1.0, 29 October 2026. Report outdated guidance through DN’s contact page with the source URL, excluding credentials.
Frequently Asked Questions
Why is my reduce-only order rejected?
Possible causes include no position, the wrong direction or position leg, an incompatible size, competing exits or other order restrictions. Use the exact error and current product documentation.
Should I turn reduce-only off to close a position?
First establish why the order failed. Removing the instruction may allow the revised order to increase or reverse exposure.
Does reduce-only guarantee my stop-loss fills?
No. It constrains exposure but does not guarantee liquidity, timing, execution price or avoidance of liquidation.
Does selling always close a long in hedge mode?
No universal rule applies. The interface may require a specific close-long action or position-leg identifier; opening a short can leave the long intact.
Why did an older exit disappear?
Some venues amend or cancel competing reduce-only orders as positions or order priorities change. Inspect order history and remaining protection.
Primary sources
- Bybit: Reduce-Only Order, updated 29 June 2026.
- Bybit: Position modes, updated 7 August 2026.
- OKX: Basic Order Types, updated 18 August 2026.
- Binance Futures: Summary of Failed Orders, updated 7 April 2026; the page warns its FAQ may be outdated, so current specifications take precedence.
- Bybit V5 API: Place Order, reviewed 29 October 2026.
All sources reviewed 29 October 2026. Operational education, not individualized trading advice.
