Here is more sample for : token = 3756033
1 minute historical data fetched for multiple days in dataframe df
df[df.date.dt.second!=0]
date open high low close volume
35588 2015-06-22 09:15:01 72.599998 72.849998 72.599998 72.699997 3881
35963 2015-…
I am facing a related issue. Have re-subscribed to KiteConnect and Historical API but Historical API says insufficient permission. Also, KiteConnect is not processing postback orders
ok i think i have not attached the correct log. I accidentally attached a log for a stoploss triggered case perhaps. (moderators may delete this post) I'll post the correct one tomorrow after re-running the test.
how to runt his in debug mode? There is no error which is thrown. I have changed my code to call KITE.holdings()['net'] instead of KITE.holdings() earlier.
KITE.holdings() gives me the following (I have not over-ridden this method):
it has 3 instr…
@ZI4453
i readjusted my code so that i collect any wrong tick right in the first line before any processing.
in any case it would be very easy for you to replicate the above problem since it happens every day for some ticks.
@sujith
I first noticed it sometime around last week of august. At first I suspected I was doing something wrong so i did not report it immediately here. It does not happen for all scripts. But it does happen everyday for about 0.1% of the ticks.
here is an example of a tick with tick['depth']['sell][0]['price'] > tick['depth']['sell'][1]['price']
{'tradable': True, 'mode': 'full', 'instrument_token': 1510401, 'last_price': 662.45, 'last_quantity': 15, 'average_price': 664.39, 'volume': …
I see. thanks for the clarification. Perhaps I used to get postback before only after modifying the stoploss values.
But this is a problem because I need the child order ids in order to modify stoploss or target of a bracket order (or am I missing …
Here is the situation:
1. bracket order placed and was checked to be complete. received postback for (creation of) parent order..
2. two child orders were automatically created since it was a bracket order (i checked this on kite.zerodha.com) but …
