Hi Sujith, I too faced the same error when tried to place order at 9.16. Recent days, I could see the API call including Place Order & Margin are failing between 9.15 to 9.20. Is it because of the overload to the API server?
@sujith Same Happened to me today. It is placeorder API using nodejs client. Last week alone I have faced this issue three times. Happening at 9.16 AM Mostly.
When an order is placed it goes through various systems and then reaches OMS. We wait for OMS to respond and then the 200 response is sent to the user. If OMS doesn't respond then Kite Trade sends this error. The ideal thing to do is to fetch orderbook and check if the order is placed or not and then retry.
@jacksonranjith, We are looking into margins not updating issue. You can follow up here.
Thanks @sujith for your quick response. Since the order API responded with exception, I don't have to Order ID to verify if the order went through or not. I can possibly check the Positions API if that works. Wondering why the Margin API failed that time, it wont required go to OMS to fetch available margin isn't it? If its your system that could respond in the initial few mins due to the heavy load, then it has to be fixed from your side. Anyway, I will followup the margin issue in that separate thread.
@sujith, I faced the API issue today (15/6) morning as well. Its not only with Order API. Positions API is also failing between 9:15 to 9:20. There is no workaround for this problem. This issue need to be fixed. Its been repeating for continuous few days. Please fix it ASAP.
Hello, @sujith I do agree with what @jacksonranjith posted. I do get the same error today also. Kindly work on that. API is failing most of the time in the morning.
What Kite Connect client are you using?
@jacksonranjith,
We are looking into margins not updating issue. You can follow up here.
Since the order API responded with exception, I don't have to Order ID to verify if the order went through or not. I can possibly check the Positions API if that works. Wondering why the Margin API failed that time, it wont required go to OMS to fetch available margin isn't it? If its your system that could respond in the initial few mins due to the heavy load, then it has to be fixed from your side. Anyway, I will followup the margin issue in that separate thread.
@sujith I do agree with what @jacksonranjith posted. I do get the same error today also. Kindly work on that. API is failing most of the time in the morning.