It could be because of a lot of reasons it might because of the lease line, could be because of network drop at OMS or Kite trade to OMS or client internet connection with Kite trade. You need to catch the exception check orderbook and then retry if the order is not placed.
But time shall indicate which hop it failed. Though order got "timed out" but it was placed and executed. more importatnly, i had placed order when there was surge in price so load on servers as well. Has Zerodha done any check if there were more fallout then normal? I faced issue in morning as well, where MKT order rejected for out of range. its generally mean that there was delay in posting order to exchange.
You need to catch the exception check orderbook and then retry if the order is not placed.
But time shall indicate which hop it failed. Though order got "timed out" but it was placed and executed.
more importatnly, i had placed order when there was surge in price so load on servers as well.
Has Zerodha done any check if there were more fallout then normal?
I faced issue in morning as well, where MKT order rejected for out of range. its generally mean that there was delay in posting order to exchange.
I never had such issues in last 10 months or so.