Imagine this: you’ve placed a stop-loss order on Zerodha, confident that your trade is protected. But as the market takes a sharp turn, your screen freezes, and later you realize… your stop loss never triggered. Sounds scary? It’s a situation more common than you’d think.
Over the past few years, “Zerodha stop loss not working”, “GTT failed to execute”, and “Kite stop loss glitch” have been trending search queries. From high volatility days to random app freezes, these issues have caused frustration and, in some cases, serious financial losses for traders.
Let’s break down why these stop-loss glitches happen, share real user experiences, and show you how to fix or avoid them.
Why Is Stop Loss Not Working in Zerodha?
Now, when the app shows any issue in order execution, it could be due to any reason. But yes, a technical glitch could be one among them, and therefore it is important to be aware, so that you can take the necessary steps required.
- Heavy Market Volatility
During periods of extreme volatility—like Budget announcements or expiry days—order flow spikes dramatically. Zerodha’s servers (and even exchange connectivity) can get overwhelmed, causing stop-loss orders to lag or remain unexecuted. - Exchange-Level Connectivity Glitches
At times, the issue isn’t with Zerodha alone. Connectivity problems between brokers and exchanges (NSE/BSE) can result in orders stuck in “Open Pending” status, leaving traders unable to cancel or modify them. - Order Type Confusion
Many users confuse SL and SL-M (Stop Loss vs Stop Loss Market). A slight misconfiguration can cause an order not to trigger as expected. - Outdated App or Browser Issues
Running an outdated version of the Kite app or browser can also lead to stop-loss glitches, frozen charts, and even disappearing order books.
Real Cases: Stop Loss Failures That Cost Traders
These aren’t just isolated incidents—here are some real-world cases of Kite Zerodha glitch where users faced issues.
1. Nov 6, 2023 – Stop Loss Orders Vanish During Volatility
On a highly volatile trading day, traders noticed that their stop-loss orders weren’t visible in the Kite order book. Attempts to modify or exit positions failed, leading to massive losses for some.
One user reported a ₹2.5 lakh loss before Zerodha acknowledged the glitch and restricted new order placements.
2. June 21, 2024 – SL Orders Not Executed During Platform Freeze
Zerodha faced a major platform freeze while the Sensex was hitting record highs. Traders couldn’t place or modify SL orders, and some positions auto-squared off at unfavorable prices.
Reports suggested that the Zerodha order not executed led to losses ranging from ₹50,000 to ₹15 lakh.
How to Complaint Against Zerodha?
If you’ve faced losses because of a stop loss glitch:
- Raise a Ticket with Zerodha
Explain the issue with timestamps and screenshots. - File a Complaint in SEBI
If you’re unhappy with Zerodha’s response, file a complaint on the SEBI SCORES portal. - Arbitration in Stock Market
For larger claims, exchange-level arbitration might be an option. Traders have successfully recovered funds this way in the past.
Need help? Register with us, and get help with the Zerodha technical glitch refund. Our team will guide you to document and draft your complaint and also help in representing your case in arbitration.
Conclusion
Stop-loss glitches can be stressful, but with the right precautions, you can minimize the damage.
Keep your systems updated, double-check your orders, and stay informed about platform issues. And if things go wrong, don’t hesitate to escalate.
