@sujith / @rakeshr it has been ~1 month since I reported this issue and it still occurs. Was the team able to troubleshoot it? Or I am to patch this on my side using minute or two delay?
@sujith, yes it happened today as well but only for one out of 3-4 orders. Happened for banknifty 29300 weekly CO short call hit sl at 9:51:20 AM. I mostly have seen this happening during volatility spikes and rarely at quite times.
Today noticed t…
I do not use pnl values from /positions API but recalculate it based on latest last_price of instruments. So I am not concerned with pnl values. I have never faced issue with executing/displaying of the orders. So I am not sure what @milli is referr…
@rakeshr this happened again today during spike in banknifty ~10.18 AM. What I have noticed that the issue occurs when the volatility is high. Websocket and both postback get callback of order completion but positions response doesn't reflect the co…
09:45:31 - Received websocket order update where CO order sl got hit for BANKNIFTY20N0525600CE
09:45:31 - After receiving order completion fired /positions API from Kite JS but /positions API response still showed that above position was open.
09:45…
I did not see the issue. I have added log for order update which may cause this positions issue. I will keep checking and update here once I spot the issue again.
Not sure what is the problem. Simple trick is to place same order in Kite and observe what kind of request it sends. Comparison may point to some missing field if there is any.
You can observe the network requests in Chrome Dev tools.
@sujith it looks like order_timestamp got regression. Was something changed during above fix? This is response from /orders API.
"order_timestamp": "2020-10-28 03:53:58",
"exchange_update_timestamp": "2020-10-28 09:23:58",
"exchange_timestamp": "2…
Thanks for posting this. I was going mad thinking about scenarios why I am getting double order updates in NodeJS websockets. I haven't changed the related code in long time and since last 1-2 weeks I have started receiving 2 same order updates for …
@rakeshr whenever socket is closed, i am only logging the error events. As I found that the stacktrace was not helpful when I analyzed myself some time back. If you feel complete stack trace is helpful, I will enable the logging for it and let you …
Sure sujith, I understand. Thank you for consideration.
Edit: If not API error message, please update the margin page where user can select expiry and see the strike range allowed.
I hate to dig this up. I see that no workaround or solution was provided. I am also seeing the same issue rarely. Today one of the order I placed was immediately cancelled. I was able to notice this and placed the order again which was accepted.
Wh…
I see in kite connect Node lib, default timeout for requests is set at 7 seconds. That is not in line with 2 seconds timeout I am seeing. Also from the stacktrace I do not see exact source of the error. So i am in the dark here
Hi @sujith,
What i meant was, i rarely get timeout error from NodeJS library. So it is definitely coming from either API end or from NodeJS lib. I have not digged deeper into lib so I am unsure which entity exactly throws timeout error while pl…
Thanks for sticky. What happens when 25 modifications are reached? e.g. Lets say limit prices are being updated for the same order and 25 modifications are reached, then I presume Kite will not accept any more modifications. But can such order be ca…
@sujith thanks for quick reply. That clarifies why existing connections kept working.
From linked thread,
At the same time, only one session will be valid.
This will not affect Kite Connect apps.
When I was logged into Kite, it should have killed …
That was definitely not fixed immediately. I fiddled with orders for good 10-15 mins to place order. How much is the cooldown period that you mentioned?
I stand corrected. I see in FAQ there is mention of data starting from 2015.
I would still love to hear if there is any alternate source to get hands on data pre 2015. Thank you.
Seems to be resolved. It wasnt streaming for solid 10 minutes which gave me chills due to open position and I wasnt able to do anything. Closed it after referring LTP on another broker.
What caused this issue?
@rakeshr thanks! I have another related query.
Usually I do backfill day candles everyday around 5PM. It seems that API is not returning day candles for today. What time I can be absolutely sure that the day candles are ready to be fetched? Around…
@sujith have question about how do you process the pending orders when the system fails. This morning I had placed buy on nifty put and because OMS failed, it didnt go through.
I have tried to cancel it multiple times through API and kite but i…
Well my system depends on socket push to get notification when order is complete/filled. In absence of that not happening I will have to tweak my system, again due to API not behaving.
How come others are not raising this? Are you polling the …
Hi Sujith. That was an honest question and my observation. The issue doesnt occur every Monday but whenever it occurs it occurs on Monday. I fail to understand why it occurs on mostly on Mondays?
The issue seems to be resolved to me. I need to ask this. What was the reason of this failure when other brokers are showing correct LTP? Also what steps are taken to ensure that this wont repeat in future?
Many times the API fails to deliver consi…
Yet another proof! This is making me extremely frustrated and irritated. Simply I do not understand how do you people mess up API on Monday?? I am seriously doubting to get my APIs from elsewhere now. This is simply lost opportunities for me when I …
Thanks for clarification. I have request for this. Can you please publish the changelog about the changes where you deviate from your own documentation so that traders can adjust the systems *not during market hours* please? This has pained me many…
Noticed this as well. Especially during first half hour after market open. Many of my calls were failed on UI side which had timeout of 3 seconds for each request. So API calls /positions and /holdings were taking more than 3 seconds to complete. Wh…
I am observing the same issue. From my home computer the /positions API takes ~150ms. While from the AWS hosted server the same call takes 700-1500ms times, earlier it used to complete within 50-100ms. That is 15x performance degradation.
If it hel…
Thanks for update Vivek. This may be one off issue not in your control. But what surprises me is that how come all these kinds of issue happen on Monday? Thats how I remember them; may be wrong.
Kite Devs, I am baffled how can you mess up systems each time after Mock sessions that happen on Saturday. The purpose of mock session is to test out the system and ensure that it works. In your case I suppose you are breaking it every time.
This i…
The regression like this is not acceptable. I went through my code and see if this was caused due to my code changes during market hours! The live prices are coming through only ticker but that doesn't help the case.
Please improve your QE process,…
Sure I understand how it works. I was proposing better implementation if Zerodha is willing to implement because what you have is not the solid solution in this aspect.
Probably no efforts are taken about this specific use case from your end becaus…
Hi @sujith,
Sure I understand but what I was hoping that data would be available soon, not after 1 minute delay. See the competition Upstox API which charge much less for historical data and are able to provide the historical candles as soon as tho…
Update: I am able to access historical data. I see that there have been multiple 2k debits on my account for these renewals due to those errors. Can you please cancel future renewals and have only one month active?
Sure I can do that search. But, my humble question is if other API responses return the correct instrument_token I expect orders API to return the correct token as well. The developer need not fiddle with these patches.
I measured the response time of Kite APIs for a server hosted in Digital Ocean Bangalore and seems that the APIs are very slow taking 150-250ms to respond back. My computer to Digital Ocean connectivity is extremely fast i.e.
I noticed that my VM timezone was reverted to UTC date. After setting correct timezone as IST to VM server, I see correct dates being returned. It seems that Kite Connect JS module was doing the date formatting itself.
Please consider this as not a…
@sujith I am receiving similar error that @quadcodes is receiving on my newly implemented Node.JS backend.
There is what I get
SyntaxError: Unexpected token o in JSON at position 1
The payload received on backend for postback URL:
{ '{"placed_by"…
@sujith indeed the postback payload received is malformed JSON. I see what @quadcodes has mentioned on my newly implemented nodejs backend.
This is the error I get when I try to parse the json in JavaScript with JSON.parse() method.
SyntaxError: Un…
