I have tried the websocket postbacks and found a behaviour where in once the order is open and completed, the events are coming in the other sequence ( COMPLETE and OPEN ). Even the timestamps are same. Request to know what could be the reason. And this behaviour is mostly when the order is put to MARKET.
These are the async events pushed by our OMS vendor, we have raised this issue multiple times with them but we haven't got any resolution yet. I would suggest not to assume the order of events, it would be better to check the status of an order to carry out any task at your end.
Suppose if I am using MAX 3 websocket connections, for al the order updates, does the postback order status be streamed to all or only one of the connection.
I would suggest not to assume the order of events, it would be better to check the status of an order to carry out any task at your end.
I have another clarification based on the below discussion,
https://kite.trade/forum/discussion/7069/websocket-instrument-stream-limits-not-yet-clear-from-documentation-and-forum#latest
Suppose if I am using MAX 3 websocket connections, for al the order updates, does the postback order status be streamed to all or only one of the connection.