If your Bybit perpetual or futures stop loss did not close your position, first check which price was selected to trigger it, whether the order triggered but failed to fill, and whether the position was liquidated first. A candle touching your stop level does not, by itself, prove that the chosen trigger price reached that level or that an exit trade executed.
This guide concerns Bybit perpetual and futures TP/SL orders, not Spot TP/SL. The controls and outcomes can differ by order type, contract and account; use your own order history and Bybit’s current product rules for the final diagnosis. Official documentation checked: 28 September 2026.
Start with the three different events
- Price condition: the selected reference price reaches your trigger level.
- Trigger: Bybit activates the conditional instruction and attempts to place the exit order.
- Execution: the resulting order actually trades and reduces or closes your position.
These events are not interchangeable. A stop-limit order can trigger and remain unfilled. An order can also fail validation after its trigger. Bybit’s order execution and liquidation FAQ distinguishes conditional activation from execution. If your position is still open, do not assume that a triggered stop has protected it.
Why the chart reached my stop but the order did not trigger
Bybit lets perpetual and futures TP/SL instructions use Last Traded Price, Mark Price or Index Price as the trigger reference. A trading chart commonly emphasizes the last traded price; the mark or index may be elsewhere at the same moment. Check the reference selected on the actual TP/SL instruction, then compare that price series at the relevant timestamp. Bybit explains these choices in its perpetual and futures TP/SL guide.
Illustrative example, not a live quote: a long position has a stop at 99, set to Mark Price. Last Traded Price briefly prints 98.9 while Mark Price remains above 99. The last-price candle crossed 99, but the selected mark-price condition did not. Reverse the comparison for a Last Traded Price stop. Always check the contract and timestamp, not a screenshot of a different market.
There is a second possibility when you selected Last Traded Price: Bybit’s TP/SL Price Protection can defer a trigger when the Last Traded Price and Mark Price diverge beyond the applicable contract’s threshold. Bybit says this feature applies to qualifying Last Traded Price TP/SL on perpetual and futures, not to Mark Price or Index Price triggers; API-set orders are excluded. Thresholds are contract-specific and can change. Price protection may avoid an anomalous last-price trigger, but it can also delay an exit during a fast market. Do not treat it as a guarantee or switch it off reflexively.
Why the stop triggered but the position stayed open
Look at the triggered order’s type and status. For an entire-position TP/SL, Bybit describes a market close on trigger. For partial-position TP/SL, market and limit exits may be available. A conditional limit exit must find a counterparty at its limit price or better; in a fast move it can sit unfilled even though the trigger was valid. A market exit prioritizes execution but its final price can slip, especially when liquidity is thin. Neither choice guarantees a particular fill price.
Also examine any rejection or cancellation reason in order history. Bybit identifies possible causes such as insufficient available margin for certain conditional orders, Close on Trigger configuration, price restrictions and Post-Only cancellation. The exact rule depends on the order submitted; an error label is more useful than guessing from the chart. Bybit’s Close on Trigger explanation describes its role in reducing an existing position rather than unintentionally opening the opposite side.
Why a linked stop disappeared
For linked take-profit and stop-loss instructions, inspect the paired take-profit order as well as the stop. Bybit says that, in a partial-position TP/SL pair, triggering one conditional limit side can cancel the corresponding opposite side even if the triggered limit order has not filled. The remaining position may therefore have no active stop. This is particularly important after manually changing position size or editing one leg. Confirm both the live position quantity and every active conditional order; do not rely on the original setup screen.
Could liquidation happen before the stop?
Yes. Bybit uses Mark Price for liquidation, while your stop may use Last Traded Price or Index Price. If Mark Price reaches the liquidation threshold before the selected stop reference reaches its trigger, the position can be liquidated first. Position margin, leverage, fees and funding can change the distance to liquidation; a stop is not a substitute for adequate margin or position sizing. See our separate Bybit liquidation guide for the broader mechanics.
A practical diagnosis checklist
- Record the contract, side, position size, stop level, selected trigger reference, exit order type and exact time (with time zone).
- Compare Last Traded Price, Mark Price and Index Price at that time for the same contract. Check whether Price Protection applied if the stop used Last Traded Price.
- Open conditional-order history and trade history. Identify whether the instruction was never triggered, triggered but unfilled, rejected, canceled or filled only in part.
- Check linked TP/SL, position-size changes, Close on Trigger, Post-Only and any visible rejection reason.
- Compare the liquidation event and Mark Price timeline if the position closed unexpectedly. Save order IDs and screenshots before contacting Bybit support.
Do not place a duplicate stop blindly while an exit order is already live: first verify the position and active-order quantities. If the platform does not show a clear reason, send support the order ID, contract, timestamps, trigger reference, order type and visible status. Our Bybit order types guide can help you distinguish market, limit and conditional instructions.
Before the next trade
Choose a trigger reference deliberately; understand whether the exit becomes a market or limit order; verify the live TP/SL after resizing a position; and leave room between your stop and liquidation threshold. If you need an exit with the highest execution priority, understand the slippage risk of a market order. If you need a price cap, understand the non-fill risk of a limit order. Reduce position size or abstain when neither risk is acceptable.
Frequently asked questions
Does Mark Price touching my stop guarantee a fill?
No. It may satisfy a Mark Price trigger condition, but execution depends on the resulting order and market conditions. Check order status and trade history separately.
Is Price Protection the same as a guaranteed stop?
No. For eligible Last Traded Price TP/SL, it can delay triggering when the last/mark spread exceeds the contract’s threshold. It does not promise a fill or a specific exit price.
Do these rules apply to Bybit Spot orders?
Not automatically. Bybit documents Spot TP/SL separately. Confirm the product before applying futures instructions to a spot trade.
Sources, disclosure and risk
Official Bybit sources checked on 28 September 2026: Perpetual and futures TP/SL; TP/SL Price Protection; Order execution and liquidation FAQ; and Close on Trigger. Product rules can change, so verify the current Bybit help pages and your own account before acting.
ByDITT is an independent educational and affiliate website, not Bybit.com. A qualifying action through our link may compensate us; this does not change the need to assess the product independently. If you are considering a new account, check the BYBITDC sign-up screen for the code, actual fees, any campaign terms and eligibility in your region. No discount, reward or availability is guaranteed.
Risk: perpetuals and futures involve leverage, rapid losses, liquidation, slippage, exchange custody and regulatory restrictions. A stop-loss instruction may fail to trigger or fill as expected. This article is general education, not financial advice or a promise of protection.
