Currently i am facing issue, that the order status sequence is incorrect in websocket. "Open" status reaches after the "Completed" status, leading to a critical error this should not happen, if this is the case then relying on sockets is a complete waste since i have to recheck using API. This occurs every 1/3 orders placed please fix this ASAP
you guys should add incremental sequence number to the events so even in async the sequence will be identifiable, this is a Critical system design flaw and ignoring this is just running away from problems
Apologies for the delay. We have forwarded this to the concerned team and are currently working on an alternative process, but don't have timeline as of now.
