If this doesn’t get fixed before April 1 which it probably won't, I think kite._post or kite._put can be utilized as a workaround.
Not ideal though, these are internal methods, so treat this as temporary and have to be revalidated after SDK update…
It seems like market_protection is not even introduced as a param in python sdk
https://github.com/zerodha/pykiteconnect/blob/6b7b7621e575411921b506203b526bf275a702c7/kiteconnect/connect.py#L336-L352
Is it accurate to infer that any market order pl…
@Nivas how was this different from previous incidents ? Could you clarify. Zerodha API went down just a few seconds after market opened on a volatile day similar to earlier incidents. Although it was not for extended amount of time like the previous…
Thanks @cnavani , I am not updating disclosed quantity so figured it should stay the same and always be >10% as order gets filled but I will give it a try.
@nagavenij , are there any updates on this? Failure to modify orders on time (which is just random, only see this issue in a subset of modifications), is leading to slippage which is worsening the issue
@nagavenij , any updates on this? I also see similar error messages intermittently while trying to modify partially filled orders with disclosed_quantity param as well
I actually tried this blog as well and installed both pyopenssl and cryprography libraries that were compatible with each other. In the end, I just found the issue was arising when jupyter was installed before kiteconnect. Didnt bother looking furth…
