Hi @cvs the way this usually works… Every order generated on the trading system is reported (read submitted) to exchange and it needs to have the correct parameters + validations broker for same. There are multiple such parameters (depends on the order + user) that every order needs to have before sending it to exchanges + additional checks on the order: the ones that are required are sent to exchange with the respective validations.
The scenario you mentioned would happen and this is handled graciously to ensure we don’t run into the situation that you indicate and at the same time user experience is not hampered. Sending orders to exchanges and receiving responses are most simple part of the order execution - even in that we have tons of innovation where DEXT gets an edge.
I wish we could have shared mored, but obviously for competitive reasons we can’t. Competition including large ones replicate / follow Dhan every now and then, and as a small broker we have to be a bit reserved as such things make us vulnerable. We know that many stock broking platforms have now started building their own trading systems - so hope you understand its important for us to keep competitive edge + lots of proprietary knowledge we prefer to keep to ourselves.
I read the above post from the link you mentioned. While I prefer not to comment on other forums - just want to state that where the user has mentioned that positions were not able to square-off till 3 PM… this was a remote situation affecting less than <0.001% of orders and the connection with exchange did not comeback leaving these orders in transit; and status update for same failed… both teams (us and exchanges) were on it immediately. Yes, few of our users made losses (and also profits), but we compensated to them as good will.