The issue seems resolved after 11:59:38
This issue should have been detected from kite end on Monday itself. @sujith You should have alert system for such issues.
It was api user who has detected the issue. Even after reporting this issue you guys …
today also it was disconnected 3 times:
I have been running my system on AWS mumbai since many months. No code changed since last 5 months.
@sujith What is going on si…
i am not sure if the rate limit is 5 orders or 10 orders/second
But "Max 20k quantities + rate limit restriction" - this combination would create lots of problems for API traders.
one restriction says you have to split the large orders. another w…
Did you tried to place more than 5 orders per second? If not then please don't put your own logic to prove your thinking.
Earlier someone from kite team confirmed that instead of having per second based rate limit, they switched to per minute …
The support article says rate limit 200 orders/minute and 5 orders/second.
Last time when I checked you told that only limitation is 200 order/minute (https://kite.trade/forum/discussion/5611/whats-rate-limit-for-kiteconnect-modifyorde…
If this is a consistent issue then, can you send the traceroute?
Last time I faced similar issue from 12 Dec 2018 to 1st week of Jan 2019. @Vivek reported this to aws and cloudflar I guess.
This time I am facing this since 3rd April consistently. …
Hi @Vivek , @sujith
We have started facing same issue again. Earlier placeOrder API was taking around 150 ms but now it takes more than 500 ms since 03-APR-2019
I am using AWS Mumbai server. Last time you mentioned that there was increased latenc…
Few of orders are triggered before trigger price hit in SL-M order (upstox) using API data. To cross verify chart show never trigger price hit.
Yes that could be possible. Take example of SBIN on 28-Mar-2019. Daily chart shows high of 339.65 while 1…
@sujith I logged in at 8.35 today so my algo worked without any issue and all the orders were going through.
Just want to understand how kite login works. Does it have dependency on OMS vendor? I don't think it should have.
Just asking be…
Thanks @HowUTrade, at least I am not only one who is facing this issue.
But I don't think Kite team would have added delay in order request. What could be the motive?
@sujith @Kailash could you please give your inputs here? I am facing this issue …
Actually I want to understand difference between below two messages:
RMS:Blocked for nse_cm DHFL-EQ BO block type: NON-SQROFF
RMS:Blocked for nse_cm RCOM-EQ BO Remarks: Please select CO product instead of BO block type: ALL
What I could und…
when I can modify the target order? until new circuit limit opened, I can't modify the target right?
Let's say LTP is 200 and circuit limit band is 190 and 210.
I executed BO SELL at 200 and kept target as 10.
Now when can I increase t…
Yes, Cancelling order is one option.
What I am doing currently is: wait for 60 sec, if order is Still open then modify the limit with current price (only if LTP is within 0.5% of my original limit price)
Yesterday, One of my Li…
I have one doubt reg bonus adjustment in kite data.
I can see there some price mismatch beetween Kite data and NSE EOD data.
For example TCS share:
For 17-June-2009, NSE EOD OHLC is (392.00 395.00 375.00 379.15)
I am not sure that Kite chart data is Dividend adjusted or not. (I verified that it is split-bonus adjusted).
Take example of COLPAL.
Latest Ex-Dividend date for this stock was 18-12-2017. 400% dividend was announced.
As per theory (https://zerodha…
As you mentioned execution range for future is 5% of reference value. Just to confirm this I placed BO in LUPIN MAR 18 fut.
Buy Price : 764.2
Target : 100.0 (864.2)
Stoploss : 1.0 (763.2)
When Order was executed, the target price was …
i am using kite 3 java client.
When I tried to place order using api, i got below error:
****Fri Feb 23 09:32:52 IST 2018 null
Is there any problem with above endpoint? which endpoint i should use till you make the final changes? This is blocking my program.
I was not facing this issue when i was using kite2 java client.
I upgraded to kite3 yesterday and si…
I think this is an error. As you mentioned in similar thread https://kite.trade/forum/discussion/2465/getohlc-api-gives-incorrect-close-price#latest close price is updated at morning 4.00 hrs.
I tried to call getOHLC api at 8.45 AM morning…
I have downloaded the kite3 java jar yesterday from https://github.com/zerodhatech/javakiteconnect/tree/kite3/dist
Do I need to re download the jar again to get correct endpoint? If not then could you please give correct end point here…
below is the error log:
com.neovisionaries.ws.client.OpeningHandshakeException: The status code of the opening handshake response is not '101 Switching Protocols'. The status line is: HTTP/1.1 400 Bad Request