@rakeshr I am facing the same issue. This issue has been particularly arising since the naming convention of trading symbols of weekly BANKNIFTY options changed. Before it used to be BANKNIFTY03JAN27500CE, and now it is BANKNIFTY03JAN1927500CE (the …
I have already contacted them. They have said that the system would square off the BO position at 3:20. However, I still have the position open. How is this possible? Why did the system could not square off the BO one?
Another issue with BO orders -
I placed a BO order for AXISBANK Sept futures today. Both the target and stop loss legs got executed. I have attached a screenshot of the target order history. It does show that a cancel signal was…
I placed an Bracket order today to buy LUPIN18SEPFUT (see order details below) with a target of 0.7
Quantity 700 / 700
Avg. price 928.5 (Executed price)
Trigger price 928.45
Order type LIMIT
The order …
Do you mean that the initial BO order will be split up into multiple legged orders?
For example - I placed an order to buy 2 quantities, and they got executed at different prices. So, there are two target orders and two SL orders for each …
Another follow-up question - In case I wish to buy/sell multiple quantities using the above method (market order mocking), will target/stop loss be now calculated based on the "average" executed price?
@sujith, thanks for clarification. I have the following query.
As you mentioned that a market order execution can be mocked by placing a limit order above LTP, will the target will be calculated upon the executed price or the order price?
I saw the link thread and think that the possible reason for my case could be no. 2
2) Order queue from the broker. Every broker is connected to exchanges via leased lines. These lines have a certain order per second capacity, if more th…
I have been facing this issue too when there is a reconnection. Does the handler gets some how disconnected on a reconnect?
Also, I receive a message on reconnect - No handlers could be found for logger "kiteconnect.ticker"
@sujith Can you please …
I am referring to minute candles (intraday).
For example -
When you run the below in Python for May 30 (today)-
kite.historical_data(1510401, '2018-05-30 14:50:00', '2018-05-30 14:52:00', 'minute')
This will return candles from 14:50 to 14:52 (3…
@sujith my question is different. I understand that the last minute candle might not be synced with the clock time at my end.
However, the date interval inclusion should be consistent. Even if you make the API request right now (after market hours)…
In my Python code, I create a 'kite' object with the api_key and then make API calls using that object throughout. It works for some calls but fails for others. I think something else is the issue.
kite = KiteConnect(api_key=my_api_key)