An Exit Order Stuck For 40 Minutes On Expiry Day: How We Recovered ₹8,970 Through Smart ODR?

Quick Summary

Subhash Barman (name changed) had a profitable options position that his broker’s app refused to let him exit. The order sat “open pending” for over 40 minutes on expiry day, while every modify and cancel attempt returned an internal error. His claim stood at ₹20,000. After a formal legal notice and escalation through Smart ODR, backed by screen recordings and the broker’s own admissions, the matter resolved with a recovery of ₹8,970, about 45 percent of the claim.

Imagine watching your profit vanish in real time because a single button on your screen will not work.

That’s exactly what happened to Subhash Barman (name changed) from Siliguri, West Bengal: his broker’s app kept rejecting his cancel order, throwing the same internal error every time.

Stop Loss Order Stuck “Open Pending” on Expiry Day: What Happened

Subhash held 120 units of an index call option on a weekly expiry day. He had bought it at an average of ₹174.35, and the position was in profit.

At 2:28 PM, he placed a stop loss sell order to protect that profit.

His broker’s app showed the order as “open pending” and kept it there.

Modify And Cancel Both Failed With An Internal Error

When Subhash tried to trail the order and then exit, the app refused. He pressed Modify, then Cancel, then answered yes when it asked if he wanted to cancel the order.

Each time, the screen said, “An internal error occurred.”

His screen recording shows the order still open and pending at 3:02 PM and again at 3:03 PM.

Why Could He Not Exit the Trade?

During those minutes, his position showed a profit of ₹5,472 to ₹8,190. The contract was trading as high as ₹242.60.

He could see the profit on his screen. His own system would not let him take it.

Anyone whose order froze this way can start a complaint against stock broker glitches using screen recordings like this one.

Why Broker Support Told Him to Wait?

Subhash called the broker’s support while the order was frozen. The representative said it would be done in a few minutes, and that it would simply process.

He was asked to give it a little time. The order stayed frozen, and the minutes ran on.

How the Broker’s Written Reply Admitted the Glitch?

Weeks later, the broker replied in writing to his service ticket. It admitted that some users saw orders stuck as “open pending” or “modify pending” on that day.

It also said his order was rejected at 3:10 PM, and all positions were correctly updated by then.

That put his frozen order at more than 40 minutes.

A Claimed Fix At 2:35 PM That Was Not True

The same reply said the issue was fully resolved by 2:35 PM. His own screen recording contradicted this, with error messages still on screen at 3:02 and 3:03 PM.

The broker’s statements did not agree with each other.

One said resolved at 2:35 PM, and another said corrected at 3:10 PM.

Why the Broker Cancelled Orders Without Client Consent?

On a recorded call, the escalation team explained what happened. They said it happened because of their platform, because the platform was theirs.

They also said clients had been placing orders multiple times during the problem.

So the broker cancelled all orders in the affected period on its own decision.

An Order Status That Misled The Client

That means Subhash’s order was neither working nor rejected for over 40 minutes.

Yet his app kept showing it as open pending.

He was never told the broker would cancel it. A client must be told promptly whether an order was executed or not.

How This Violates SEBI’s Technical Glitch Rules?

SEBI’s January 2026 circular on technical glitches in brokers’ trading systems defines a glitch plainly.

It is a malfunction in order placement, modification, cancellation, execution, confirmation, or status, lasting five minutes or more.

Subhash’s order sat frozen for over eight times that. The broker’s own words matched every element of the definition.

The stock broker regulations also require a broker to execute client orders promptly, as the client instructs. His instruction was to exit, and the system refused it.

How We Built The Compensation Claim?

The case rested on a screen recording and the broker’s own written and spoken words.

We built it in six steps:

Step One: We Fixed The Timeline Minute By Minute

The order time, the two error screens, the profit range, and the 3:10 PM rejection were laid out on one timeline.

Together they showed a freeze longer than 40 minutes.

Step Two: We Quoted The Broker’s Written Reply

The admission about orders stuck in open pending was set beside its claim of resolution at 2:35 PM.

The mismatch became the core of the notice.

Step Three: We Transcribed The Escalation Call

The statements that the problem was the platform’s fault, and that orders were cancelled on its own decision, were typed out with translations.

Step Four: We Showed The Profit That Could Not Be Taken

The profit shown at 3:02 and 3:03 PM was recorded as the loss of opportunity. We compared it with the final loss on the position.

Step Five: We Sent A Formal Legal Notice

Our notice cited the glitch circular, the duty to execute orders promptly, and the duty to report an order’s status. It gave the broker a clear window to respond.

Step Six: We Escalated To Smart ODR

When the notice did not settle the matter, we filed on Smart ODR with the recording, the ticket reply, and the call transcript attached.

₹8,970 Recovered Through The Smart ODR Process

Subhash’s claim stood at ₹20,000.

Through the Smart ODR process, the matter was resolved with a recovery of ₹8,970, about 45 percent of the claim.

Broker statement screenshot showing 20,503.96 highlighted in red supporting the ₹8,970 Smart ODR recovery
Statement record used to support the ₹8,970 recovery through Smart ODR

Was Your Order Stuck While The Market Moved? Our Team Can Help

Record your screen the moment an order freezes, and save every ticket reply.

If your broker’s system failed you, Register with us and we will build the case from those records.

Conclusion

Subhash’s claim was small, and the lesson is large. A stuck order on expiry day can turn a profit into a loss within minutes, and a client cannot prove it later unless he records it as it happens.

His case also shows how a broker’s own words build the claim. One message said the issue was resolved early, another said it was corrected later, and a recorded call said the platform was at fault.

A recovery of about 45 percent reflects what the documents could prove at the stage the matter settled. We say so plainly, since glitch claims often depend on how much loss a client can tie to the freeze.

If a notice to your broker stalls, the Smart ODR complaint portal takes the same records into a structured forum.


Report. Recover. Stay Fraud Free.


Frequently Asked Questions

A malfunction in order placement, modification, cancellation, execution, confirmation, or status for five minutes or more counts as a technical glitch.

A broker must promptly tell you whether an order was executed or not. Cancelling orders on its own decision, without informing you, can be challenged.

Record your screen showing the order status, the error message, and the time. Then save every ticket number and written reply from the broker.

Yes, if you can prove it. Note the date and time of the call, and ask for the ticket to confirm what was said.

Yes. Smart ODR accepts claims of any size, and a clear screen recording with the broker’s own reply makes even a small claim strong.

loader

FraudFree Support

We're online — reply instantly
Scroll to Top