All users were in different networks.
Stacktrace:
2022-05-17 15:44:38,856 ERROR – Error in GetOrderBook InnerException: =>
2022-05-17 15:44:39,671 ERROR – Error in GetOrderBook Message: =>
The remote name could not be resolved: 'api.kite.…
We have upgraded the library.
This problem has happened 5-6 times. I can share the logs of each and every instance with you if you want.
But please don't ignore it there is definitely some issue.
Hi, @tonystark Thanks for your reply. It's not happening with any particular instrument. It's happening with nifty or bank nifty options randomly. Also, it's not happening with a few users randomly. We have reported around 5-6 instances so far. Init…
Again, please note, that if the issue was in our programming then it should happen with all of our clients. But it's not the case.
Rarely it's giving this issue.
Hope this time I will get a satisfactory answer.
One thing I have observed is, The LTP at that time was around 271-272 and the tick we received was 27175. So I think the problem is with the decimal conversion. We're using .net C# API. Can you please check the logic for the same?
Hi Sujith,
today it has happened again.
Wrong tick for BANKNIFTY2242136800CE at around 10:29:08.
One thing I have observed is, The LTP at that time was around 271-272 and the tick we received was 27175. So I think the problem is with the dec…
I understand it and it has never happened before for us too.
But only one user got this issue. We have verified logs at our end and the LTP was captured 437.5 only.
Can you advise how we can track this issue?
Please check the attached image. For stock, OHLC is available but for index it's N/A.
Kindly correct this immediately.
We can't store high low every day to use on the next day because the user forgets to run it for a day next day high and low won't …
I just checked it and understood the changes you suggested. Thank you very much for your wonderful support. I will try it tomorrow and will share my feedback.
@rakeshr I didn't understand this part: "nor we found anything on logs for your connection."
Are you saying you're not finding anything related to the error or you're not getting any logs at all about connection? We're running it every day.
I am se…
I didn't get you. We've been running it every day so you must be seeing some logs I think. We're running it on AWS and I have tried with two different machines as well. but the result was the same.
@sujith
I have tried the following combinations:
kiteconnect==3.9.2
Twisted==20.3.0
__________
kiteconnect=3.8.2
Twisted==20.3.0
But both the versions failed with the same error.
I am sending you the API key in personal.
Thanks
@sujith Yes, it happened today also.
It was working fine for a long time. Our system was stable for a long time and suddenly it started happening for the last 5-6 trading.
@sujith you didn't get my question.
I think portfolio/positions don't get updated live. So if one position is taken in any symbol, how much time it will take to be reflected in the portfolio/positions API call response?
@sujith
I was reading the whole thread about the PNL calculation.
You've mentioned that we can fetch the multiplier from the position API call. May I know at what interval do we get the updated positions via this call? Multiplier will be required …
Thank you @sujith
It doesn't happen everyday. I have observed it twice in this month.
If it happens again, I'll let you know.
Appreciate the quick resolution
Regards,
Rishi A.
The candle high is 1098 and error message says LTP is 1112.45. So you're saying that in a liquid stock like INFY there was just one tick with a difference of 15rs and it was not captured?
@rakeshr I believe the day high and low in the market depth comes from NSE. (Let me know if I am wrong) The day high is 1109.7. Price never went to 1112.45 which is mentioned in the error message. Could you please check again?
Yes, I have checked it @sujith.
In such a scenario, you are asking to check in the order book if that order actually went through or not.
Now the problem is, we're sending multiple market orders with same parameters. In that case, guessing the orde…
@Vivek @mapreduce I am still facing the same issue. I checked the data type of instrument token as well and it's native int only. Any idea what could be the issue?
Hello,
I am a python developer. I have knowledge of technical analysis and trading terminologies. I can help you develop the codes for algo trading. Please have a look at my profile and portfolio to get an idea about my capabilities and some previou…
Hello,
I am a python developer. I have knowledge of technical analysis and trading terminologies. I can help you develop the codes for algo trading. Please have a look at my profile and portfolio to get an idea about my capabilities and some previou…
Hello,
I am a freelance developer. You can reach me at [email protected] | +91-9099996590.
Here's the link to my profile: https://www.freelancer.in/u/rishiajmera
Thank you
Regards,
Rishi A.
Hello,
I am a freelance developer.
Please send me more details on [email protected].
Here is the link to my freelancer.com profile.
https://www.freelancer.in/u/rishiajmera
Regards,
Rishi A.
+91-9099996590
@sanampatel At some places in the function, Open, High, low, and Closes are hard-coded instead of using function arguments. So you need to find them and change it with arguments.
@arkochhar Hey, Thanks for replying. Yes I have done that. and I also replaced the 'close' in the code with ohlc[3] inside the function.
I even removed the ['Open', 'High', 'Low', 'Close'] candles from the data frame and passed just the ['HA_Open', …
@arkochhar When I try to give Heiken Ashi candles as input to calculate the super trend, it gives super trend based simple ohlc candlesticks, not based on Heiken Ashi candles. Can you please suggest some solution?
By 09:08, the Open price is decided for few stocks only. not all the stocks. I think you will be able to fetch it by quote() call.
I hope this will help.
Thanks,
Regards,
Rishi A.
+91-9099996590
@Vivek , Thanks for the reply. Yes, I'm passing the request token and API secret correctly. I've generated the 'request_token' as described in the login flow. Still, I'm not able to generate the access id successfully.
