Inconsistent rms rejections at dhan

@Dhan_Help @PravinJ ,
I have been having tough time with DHAN on 4th and 5th of December 2023 while executing my strategies with DHAN , incurred heavy losses as well. Though I have been executing my hedge legs quite in advance 10 secs prior to SELL legs , it kept on rejecting with RMS errors, not allowing PE leg to execute. I have enough margin in my account. I checked through margin calculator too. I just attached one of the instance on 5th of Dec, can be easily seen the reported times from DHAN , buy legs executed 10 mins prior to the sell leg. Kindly check.

Hi @jacharjya1978 Please share your user details with our Customer Service team on help@dhan.co, will review the log. Only possibility is margin blocked for pending orders, however we will have team check the logs and confirm.

UCC : VPFZ33006F
Client ID : 1100255178
@PravinJ , This RMS error on fund insufficient becomes a regular occurrence with DHAN now a days. Today too I incurred a good amount of loss. Don’t have enough confidence with DHAN now.
I have sufficient fund 10 Lacs plus , which is enough to execute my strategy of 12 lots of Bank nifty iron condor, where 1 lot needs around 70 thousand , 12 lots around 9 Lacs.
Hedge legs executed way before (10 secs before) the risk legs. Still RMS throws error.


Later Even I tried with 10 lots , still has similar RMS error.
I execute the same strategy everyday , many days it goes fine. However I literally scared not sure when Dhan will give surprise . I lost 5K today.
I will raise another issue which is on no. of orders restriction over api , there also DHAN blocked my strategy , its a frustrating day with DHAN.

1 Like

@PravinJ
The second issue today , rate limit per hour exceeded , for my Nifty Iron condor strategy , which is a simple strategy with hedges. Only trailing for sell legs on 15 % of move trail 10 percent , which is not aggressive. Not sure how DHAN arbitrarily block these executions.


Hoping a convinced response from DHAN team.

Hello @jacharjya1978

We checked logs for this order. Over here, the second sell leg (for 47400 PE) was sent while the first sell leg (48600 CE) was being executed. This is the reason for the second leg getting margin error as the hedge wasn’t created.

On the Rate Limit issue, we have already increased Non-Trading API per hour rate limit, especially for AlgoTest. We are figuring out with the Algotest team to avoid such scenarios further, and probably change API polling rates at their end.

@Hardik Thanks for responding .

  1. Will add a one sec delay for the 2nd sell leg , hope it would be seamless execution going forward.
  2. Kindly work with AlgoTest to resolve this kind of errors. It would help the community a lot.
1 Like

Hello @Hardik , @PravinJ
I am again getting inconsistent RMS rejections , losing all the earning potentials , my strategy has an abrupt end because of this errors. Here is the one of the case today.



My Margin available : 14,25,976
Aprox Margin required for my Strategy : 35 * 36 = 1,260,000
Rejection Reason : Response for Rejection
RMS:42240515648201:Fund Limit Insufficient By 5689.98 & Available Amount 395018. Order Amount Is 9090.00

Lost earning potential of 7500 today , as I am running similar strategy in another broker , it was seamless.

Second issue:
I have been following with @dhancare since last one week , not getting any satisfying answer.
My orders are rejected because of rate limit per hour. I doubt its something with modification of orders. I have something like this.
Selling a leg with 15 rupees premium , 23 as stop loss. TSL 1/1 , so at max it would trail 15 times i.e 15 modifications per order . Dhan allow 25 modifications per order.
why its being rejected.
Note : I have similar kind of strategies in other brokers , its seemless. I am having all these issue with DHAN only.

Regards,
Sunita

1 Like

@PravinJ @Hardik
Today also same story
I have sufficient margin , still RMS rejection


@ 10:13:59 22050 PUT sold , SL executed @ 10:20:57 , not sure why DHAN shows time (without clearly showing its order time) which creates confusion.
The new SELL leg NIFTY 16 MAY 22050 PUT ordered @ 10:20:59 (post 2 secs )

RMS still rejected , whole my strategy disturbed .

Its becoming a regular story with DHAN. My similar strategies running fine with free brokerage brokers. Its been 1 and half years my stay with DHAN. Now I decided to leave with a heavy heart. I can’t have headaches every now and then with DHAN.

All the best !!!
Good bye.

Hello @jacharjya1978

On the first one, can you tell me the source of the order? Are you using any of the Dhan platforms or your algo to place trades. If it is algo, then can you share the Order JSON through which you are placing order? Also, do check in case you have any other pending orders also at that moment.

On the second one, it shouldn’t be order modification error. Can you please send the error message that you are getting and any past order records, will get this checked.

Both these scenarios are non-intended and we will resolve this as soon as possible. We are committed to assist you with all your queries.

Hi @Hardik ,
On the first one, can you tell me the source of the order? — ALGOTEST
Also, do check in case you have any other pending orders also at that moment. : NO PENDING ORDERS THAT TIME.

I already put the timings and shared the screen shots. Its quite well known DHAN RMS very slow to react. I am having these issues quite often. I had similar issue yesterday as well as today too.

On second issue . This is also quite often when you have TSLs setup. You can refer the below error.
unknown error=Per Hour Rate Limit Exceeded For Orders API.
Its been one week , I just asked DhanCare …give me a simple example of valid and invalid pricing to set the limit for Nifty options. I am still waiting.

After all this headache , may be I am not made for Dhan , decided to wind it up.

Hello @jacharjya1978

We regret that your experience was not upto the mark here. On RMS speeds, we are sure that this execution problem is not on DEXT layer.

Since it is a partner platform where you are facing the issue, we can connect with Algotest team to resolve this and check on the logic where the per hour rate limit for Orders API is being reached (this is first time that we got this). Can you DM me your Client ID and we will take a look on this.

With LPP, the range is defined here: Limit Price Protection (LPP) on Trading in Index Options.