Hello,
Can you please help me understand what are the order updates receive on web socket that can tell if a SPOT Stop Loss Limit order was triggered?
I noticed that for USDM or COINM when a stop limit order is triggered we receive on web socket an order update with status “NEW” and order type field changed from “stop Limit” to “limit” and the order is updated also in the Web interface.
For SPOT when a Stop Loss Limit order was triggered we receive on web socket an order update with status “NEW” but the order type is not changed and the order remains the same in the Web interface. Can you please tell me if this is intended or if the order type should change too like in the USDM or COINM case?
Thank you!
If you are listening to the websocket user data stream, the underlying order is created the moment the stop order is activated, with the new underlying order having an order type of MARKET or LIMIT.
For questions regarding the UI, I suggest directing the question to Binance Customer Support.
Then maybe there is some issue with updates received for the underlying order on SPOT? From what I noticed the underlying order has order type “stop loss limit” and not “limit”, at least this is the value for the order type received on web socket for SPOT orders.
This should not be the case. Please provide samples events from production so that we can further diagnose.
I think I clarified the question on the telegram channel. It seems that for SPOT the order update for the order limit triggered by a stop limit order has the flag which says if the order is or isn’t on the book (“w”) set to “true” and for FUTURES the order update for the order limit triggered by a stop limit order has field order type (“o”) set to LIMIT. Thanks for the help.