Stop Loss Not Triggered

Created by Pawan Kumar, Modified on Wed, 29 Jul at 11:42 AM by Pawan Kumar

If your Stop Loss (SL) order did not trigger, it does not always indicate a system issue. Stop Loss orders are executed only when the market reaches your specified trigger price and the order meets the exchange's execution conditions.

Common Reasons Why a Stop Loss May Not Trigger

1. Trigger Price Was Not Reached

Your Stop Loss order is activated only when the market price reaches or crosses your specified trigger price.

2. Market Price Moved Too Quickly

During periods of high volatility, the market may move rapidly, causing the price to skip over your trigger or execution price.

3. Insufficient Market Liquidity

If there are not enough buy or sell orders available at your Stop Loss price, your order may remain pending or be executed at the next available price.

4. Order Was Cancelled or Modified

If the Stop Loss order was cancelled or edited before the trigger price was reached, it will not be executed.

5. Incorrect Stop Loss Configuration

Please verify that the trigger price, order price (if applicable), and quantity were entered correctly when placing the order.

What You Can Do

  • Check the order status in your Order History.
  • Verify the trigger price and execution price you entered.
  • Compare your order details with the market price at the time.
  • Review whether the order was cancelled or modified.

Need Further Assistance?

If you believe your Stop Loss should have been triggered but was not, please raise a support ticket and include:

  • Your User ID
  • Order ID
  • Trading pair
  • Stop Loss trigger price
  • Date and time of the order
  • A screenshot of the order details (if available)

Our support team will investigate the order and assist you as quickly as possible.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article