Dhan broker stop-loss complaints: why orders fail often

Why Dhan stop-loss execution is trending

Complaints around Dhan stop-loss behaviour have been circulating on Reddit and other social platforms. A recurring theme is that traders believe their stop-loss orders are not being handled as expected in fast moving option and index trades. Some posts describe stop-loss orders being declined repeatedly, while others claim orders execute immediately even before the stop level is reached. There are also reports of being unable to place orders at all on a particular day, alongside frequent connectivity issues across BSE, NSE, and MCX. In the same threads, users also discuss practical reasons why stop-loss orders can remain open after being triggered, especially with stop-loss limit orders. The discussion is not limited to execution alone and includes product integration and order modification limitations when using TradingView. Dhan’s responses shared by users repeatedly ask customers to connect with the support team through the app and share trade details for review. The combination of alleged order issues, platform constraints, and escalation routes is why the topic has stayed active online.

TradingView integration: modification limits users report

One of the most repeated complaints is specific: a stop-loss order placed after buying options cannot be modified on TradingView. The user posting this said it is their only problem and expressed hope that Dhan will address it in a future update. Another user’s interpretation in the same discussion is that the constraint appears to stem from limitations imposed by the broker rather than the charting software itself. That point matters because it frames the issue as an integration capability gap rather than a simple TradingView feature request. Traders using TradingView often expect to adjust risk quickly, especially when premiums move sharply or spreads widen. When modification is not available in the linked workflow, the trader may have to switch back to the broker app or web terminal to make changes. That extra step can be material during volatile moments, even if execution works normally. The same online threads underline the need to understand integration capabilities before placing complex orders. As of the posts shared, the complaint remains focused on modification, not on the ability to place a stop-loss itself.

Stop-loss limit mechanics: why orders can remain pending

A key part of the social discussion is the difference between being triggered and being executed. Users referenced the behaviour of a stop-loss limit order, where a trigger converts the instruction into a limit order rather than guaranteeing a fill. The example shared explains that if a sell stop-loss has a trigger price of Rs. 91 and a limit price of Rs. 90.90, the order will try to execute at Rs. 90.90 or higher after trigger. If the last traded price drops quickly below the limit price, the order can remain open and pending rather than executing. Posts attribute this risk to volatility, expiry conditions, lack of liquidity, and special events. Another factor highlighted is high bid-ask spread combined with multiple market orders, which can cause price jumps. In that scenario, the time between trigger and exchange execution can matter if the price moves beyond the limit. The discussion repeatedly returns to a practical takeaway: stop-loss limit orders need a sufficient range to reduce the chance of a trigger without execution. At the same time, traders also note that widening the range too much can defeat the purpose of a tight stop-loss.

SL-Limit vs SL-Market: what users say is allowed

The threads also reference product constraints that affect how stop-loss protection works in different instruments. One post states that a stop-loss market order gets executed immediately at the market price once triggered, but it is not allowed in options as per exchange. In contrast, stop-loss limit is presented as a tool for managing risk within a desired range, with the known trade-off that execution is not guaranteed if price gaps. Another Dhan-oriented note shared in the discussion says SL-Market is allowed in Equity and Futures only, while stop-loss orders can be placed in both forms depending on the instrument. The implication for options traders is that they may be restricted to SL-Limit type behaviour in practice. That restriction can amplify complaints during rapid moves because a limit-based stop can be skipped in illiquid or fast markets. Traders in the threads suggest checking liquidity and bid-ask spread when deciding the gap between trigger and limit. The same posts frame this as a best estimate rather than a fixed rule, because spreads and liquidity change across contracts. Overall, the online discussion links many perceived stop-loss failures to order type limitations and market microstructure.

Reports of declined stop-losses and immediate triggers

Beyond order mechanics, some social posts describe behaviour that users attribute to the broker platform. One user says their stop loss orders are consistently being declined, without detailing the exact rejection reason in the quoted text. Another user claims that when placing a stop-loss order on the Sensex, it gets executed immediately even if the price has not reached the stop-loss level. The same person says they were unable to place any orders at all on September 20, 2024. They also mention market buy and sell orders not executing and describe connectivity problems across BSE, NSE, and MCX. According to that post, despite numerous complaints, customer support insisted everything was working fine. These are user allegations and are not independently verified in the shared context, but they reflect the nature of complaints being discussed publicly. Such posts often prompt other traders to ask for details like timestamps, order IDs, and screenshots, because execution issues are hard to diagnose without trade logs. The common thread is not just dissatisfaction, but uncertainty over whether the root cause is order type rules, connectivity, integration limits, or broker-side constraints.

Common pain points mentioned by traders

The discussions cover several distinct issues that traders often mix under the single label of “stop-loss not executed.” Some complaints relate to modifying stop-loss after entry on TradingView, while others relate to execution outcomes after trigger. There are also operational complaints about not being able to place orders, and about orders being declined. Another cluster of posts is about education and expectations, especially around SL-Limit behaviour and the need to set a gap based on liquidity and spread. Dhan’s own support replies, as shared by users, focus on case-by-case review through app support and trade details. The table below groups the main issues raised in the context and the likely area they relate to, based only on what users described. It helps separate integration limitations from market-structure outcomes and from alleged platform outages. Traders reading these threads typically use such categorisation to decide whether to tweak order parameters, change workflow, or escalate a complaint. While the context does not provide final resolutions, it clearly shows what is repeatedly being reported.

How Dhan says stop-loss can be placed from Positions

Amid complaints, a practical how-to was also shared for placing a stop-loss for an open position through the Dhan app or web. The steps described start from logging in and going to the Position tab. From there, the user should tap on the scrip name and select “Naked Position - Add Stop Loss.” The posts say stop-loss orders can be placed in both forms, namely SL-Limit and SL-Market, with the note that SL-Market is allowed in Equity and Futures only. For options, the same discussion references that stop-loss market is not allowed as per exchange, implying SL-Limit is the relevant tool. This workflow matters for traders who are relying on TradingView for entries but need broker-terminal controls for risk management. It also helps isolate whether the problem is about stop-loss placement itself or about modification and monitoring. Some traders may use this route as a workaround if TradingView-linked stop-loss modification is not available. The shared context does not specify whether this method resolves the reported declines or premature executions, but it is the most concrete operational instruction provided.

Dhan support, grievance emails, and compliance contact

Dhan’s responses quoted in the discussion repeatedly ask users to connect with the Support team through the app and share trade details so the team can review and assist. For general queries, feedback, or clarifications, the email shared is help@dhan.co. For grievances about services rendered by Raise Securities Private Limited, users are asked to write to grievance@dhan.co for NSE, BSE and MCX, or grievancedp@dhan.co for Depository Participant related matters. The compliance officer details shared in the posts list Mr. Manish Garg, with mobile 8655740961 and email complianceofficer@dhan.co. Users also reference an option to lodge complaints using SEBI SCORES, with a link shared as part of the same escalation text. Another note included in the context states that Raise Securities Private Limited, also known as Dhan, is an order collection platform for mutual fund orders placed on BSE StarMF for execution. That text also says clients expressly agree that Dhan is not liable for non-execution or incorrect execution of orders with regard to the funds chosen, citing link or system failure and banking or payment aggregator delays as examples. While that disclaimer is about mutual fund order routing, it appears in the same social compilation and influences how users perceive accountability and escalation. For traders, the practical takeaway from these posts is to keep communication in writing and share complete trade details when raising execution complaints.

SEBI SCORES and SMART ODR: what users shared about filing

The escalation route mentioned repeatedly in the shared text is SEBI SCORES and the SMART ODR portal. The procedure quoted starts with registering on the SCORES portal. The mandatory details listed for filing complaints on SCORES are Name, PAN, Address, Mobile Number, and E-mail ID. A link is shared for more information: https://scores.sebi.gov.in/. Users also shared that there is a SEBI Scores app available for Android and iOS, with store links referenced in the posts. The intent of sharing these links in broker-related threads is typically to guide users who feel their complaints are not being resolved through standard support channels. The context does not describe outcomes from SCORES submissions, only the process and required information. It also does not provide a specific timeline or format for attaching order logs, but traders generally discuss submitting screenshots and broker responses when escalating. Importantly, the posts show an escalation ladder: app support and help email first, then grievance email and compliance officer, and then SEBI SCORES. For traders facing stop-loss disputes, following the documented steps and keeping records aligns with the process described in the shared text.

What to document before raising a stop-loss execution complaint

The repeated suggestion from Dhan, as shared by users, is to provide trade details so the team can review and assist. In practice, that means collecting the order type (SL-Limit or SL-Market where applicable), trigger price, limit price, and the instrument traded. It also means noting the time the order was placed and the time it was triggered or rejected, because some complaints relate to immediate execution or declines. Where the complaint is about TradingView, traders should capture what actions were attempted and what modification options were unavailable. Since the social discussions also highlight liquidity and bid-ask spread as potential reasons for pending stop-loss orders, screenshots of spread conditions at the time can help explain outcomes. If the issue was inability to place any orders or connectivity problems, documenting error messages and exchange segment (BSE, NSE, MCX) can support the claim. The context also mentions that some traders felt support insisted everything was working fine, so keeping written support interactions can be relevant for escalation. For any complaint route mentioned, including grievance emails and SCORES, the quality of evidence often determines how clearly the case can be assessed. The posts do not provide a checklist, but the details repeatedly referenced imply that precise order parameters and timestamps are essential.