The order status said rejected. So Karan moved on.
The broker’s backend said otherwise. The position was live, and growing.
By the time he found out, he could not exit. By the time the broker acted, the damage was ₹2.5 lakh.
This blog is about what happened, why it is claimable, and what to do if something similar happened to you.
Trading App Glitch: What Happens When Your Order Status Lies
Karan (name changed) builds trading algorithms for a living. He is not someone who misreads a screen or panics mid-session. He knows exactly how an order is supposed to behave, from the moment it leaves his terminal to the moment it fills.
That precision is what made what happened to him so impossible to dismiss.
He was managing a commodity options position near expiry. The strategy involved buying a far call and a far put, selling closer legs, then managing each position actively. He sent the orders through the broker’s app.
The app responded: “Market rejected.”
Karan read that. He accepted it. He did what any rational trader does when an order is rejected, he assumed nothing had executed and moved on.
Then he opened the actual terminal. His stomach dropped.
The far call had filled at ₹7,000. The far put at ₹100. Both orders, the ones his screen had declared rejected, were sitting live in his portfolio.
Unable to Square Off Positions Due to Broker Error
That day, there was a known technical glitch in stock market. Another broker had publicly flagged that fresh orders were not processing. So Karan’s positions sat open, live, and completely beyond his reach, while he watched the clock.
Late that night, at 11:15 PM, the broker stepped in. They squared off two legs at a brutal price, booking roughly ₹1 lakh in losses. The ₹7,000 call was left to expire worthless.
By the time it was over, the damage was approximately ₹2.5 lakh.
When Karan wrote to the broker, their response was honest in the worst possible way.
“Our system converts your market order into a limit order before sending it.”
Then they blamed the exchange.
Karan had kept everything, screenshots of the “rejected” message, screen recordings, same-day emails. He knew something had gone badly wrong. What he needed to know was whether it was claimable.
It is. Three distinct failures sit inside this one incident. Each of them belongs to the broker.
Is a Broker Liable for False “Market Rejected” Status?
This is the core of the entire situation. Everything else follows from it.
When a trading platform tells you an order was rejected, you trust that information. That is the only rational response. The screen exists precisely to tell you what is happening in your account. You cannot check the exchange backend in real time. You rely on the platform to be accurate.
If the platform showed “rejected” while the order was actually executing, the platform gave you false information. That is not a glitch you absorb as a trader. It is a system failure the broker owns entirely.
Every decision Karan made after seeing “rejected” was based on that information. The position was never monitored. Also, no hedge was placed and no exit strategy was prepared. After all, the trade should never have existed.
When Brokers Silently Convert Market Orders to Limit Orders
Here is what the broker admitted in writing: their system silently converts a market order into a limit order before sending it to the exchange.
Read that again.
Karan chose market execution. He wanted the order filled at the best available price, immediately. The broker’s system intercepted that instruction and changed it to a limit order, without notifying him, without asking, without any visible indication on his screen.
That is not an execution feature. That is a unilateral override of a specific trading decision.
Broker System Blocking Your Exit Trade
There is a principle that sits underneath all of trading: you must always be able to close your position.
It does not matter how you got into the trade, how complex the strategy is, or what the market is doing. A trader’s ability to exit is non-negotiable. It is the single most fundamental protection a retail investor has.
When Karan discovered the positions were live, he acted immediately. He tried to square off. Rejected.
He tried again. Rejected again.
The broker’s platform would not let him out. And this was not a private problem, it was a known glitch, active across the segment, documented by other brokers at the same time.
So Karan was trapped. His capital was locked in open positions. The market was moving. And the system that was supposed to serve him had made him a passenger in his own account.
At 11:15 PM, hours after he first tried to exit during trading hours, the broker stepped in. They squared off two legs at a price that had nothing to do with where Karan would have exited, had the system let him.
That forced square-off, at a devastating price, after hours of being locked out, is not routine risk management. It is the consequence of failed infrastructure acting on someone else’s account. The loss from that sequence belongs to the broker’s system, not to Karan’s strategy.
How to File a Complaint Against a Stockbroker for Technical Glitches
Evidence in trading disputes has a short shelf life. Screenshots get overwritten. Screen recordings sit in storage until storage resets. Emails get archived and buried.
Act today, not this week.
Step 1: Preserve Every Piece of Proof Right Now
Save screenshots showing the “market rejected” status. Also keep any screen recordings that capture both the rejection and the live position. Preserve all email exchanges with the broker, especially messages explaining how the system operates.
Pull your contract notes showing the fills. Save screenshots of every failed cancellation or square-off attempt. Get your trading ledger for that day.
Step 2: Write a Formal, Violation-Specific Complaint to the Broker
Do not send a vague grievance. Name each failure specifically.
State that the platform showed a false “rejected” status even though the order executed. Also state that the system changed your market order into a limit order without any prior disclosure.
Mention that you tried to square off during market hours, but the platform prevented it. Later, a forced square-off took place at a price caused by the platform’s failure rather than normal execution.
Step 3: Lodge a Complaint in SCORES
No satisfactory resolution? Take your complaint to SEBI’s investor grievance portal at scores.sebi.gov.in.
Select the stockbroker category. Upload the complaint letter, screenshots, contract notes, and the broker’s written admission about order conversion.
A filed SCORES complaint carries formal regulatory weight. The broker must respond formally. Regulators have directed brokers in cases involving exactly these platform failures.
Step 4: Raise a Complaint in SMART ODR
If SCORES does not produce what you need, escalate to SEBI’s SMART ODR platform.
A neutral expert reviews your case in a structured, time-bound process. No lawyer required. Your evidence does the work. Present it clearly and completely.
Step 5: Exchange Arbitration for the Full Amount
For a loss of this size, exchange arbitration through NSE or BSE produces a binding, enforceable award.
This process is faster than civil court. It is designed for retail investors. And it is the route through which traders with documented broker failures have recovered real money.
Karan’s case, the false status, the order conversion, the blocked exit, the midnight square-off, has exactly the kind of documented evidence that arbitration panels act on.
Get Expert Help to Recover Trading Losses
What happened to Karan is not rare. Broker platforms fail. Orders get misreported. Systems modify instructions without disclosure. Clients get trapped in positions they never agreed to hold, at prices they never agreed to accept.
Karan came to us with everything documented and a clear sense that something was seriously wrong. What he needed was a path. We are building it with him.
If your broker’s platform gave you false information, changed your orders, blocked your exit, or forced a square-off you never authorised, your loss is not yours to carry alone.
Reach out to us today. We will go through your case and tell you honestly what is claimable, before you commit to anything.
Conclusion
Karan did not make an error. He read what his screen told him and acted accordingly. When trying to exit the moment he discovered the truth.
The system blocked him at every turn, first by lying about the order status, then by changing his order type without telling him, then by refusing his exit attempts, and finally by stepping in at 11:15 PM to close positions at a price no rational trader would have accepted.
The broker’s own email confirmed how their system works. That admission does not close the matter. It opens it.
Start with your evidence. Write to compliance. File on SCORES. Escalate through SMART ODR. Take it to arbitration. Do not let “it was a glitch” be the last word.
The loss followed from their system’s failures. That is where accountability should sit.
Frequently Asked Questions
1. Karan’s screen showed “market rejected” but the order had filled. How does that become a broker’s liability and not just a technical error?
Because the platform’s job is to show you the accurate state of your account. When it shows “rejected” while an order is live and executing, you act on false information. You do not manage the position, do not hedge, and do not attempt to exit. Every rupee of loss that flows from those decisions, decisions made on the basis of what the screen told you, is traceable back to the platform’s false report.
2. The broker admitted their system converts market orders to limit orders. They say it is standard practice. Why is that still a problem?
Because Karan did not know about it when he placed the order. Disclosing a practice in a complaint response is not the same as disclosing it before the order is placed. He chose market execution deliberately. The system changed that without his knowledge. The fills, the prices, the way the position behaved, all of it followed from an order he did not actually place.
3. Karan tried to square off and was rejected multiple times. The broker says the glitch was exchange-side. Who is responsible for the fact that he could not exit?
The broker is responsible for its own platform’s ability to process client instructions. A known, segment-wide glitch does not transfer that responsibility to the exchange. Karan’s square-off requests were rejected by the broker’s system. The broker then made the decision to force-exit his positions at 11:15 PM at a distressed price. Both the blocked exit and the forced square-off happened inside the broker’s operations.
