STOP order is not triggered when the trigger price is reached

Hi guys. I can’t understand what’s the matter. In the last month, STOP orders partially stopped being triggered when the trigger price was reached (that is, a stop order is placed, when the trigger price is reached, the exchange does not cancel it and does not place a LIMIT order). Nothing has changed in the program code, I have not found any changes in the API in the change log … What could be the problem?

Sample parameters for placing an order:

{
            newClientOrderId: '1612187015976',
            symbol: 'BTCUSDT,
            side: 'SELL',
            positionSide: 'BOTH',
            type: 'STOP',
            quantity: '10',
            price: '32000',
            stopPrice: '32300',
            timeInForce: 'GTC',
            newOrderRespType: 'RESULT',
            recvWindow: 60000
}

This is strange, I can’t reproduce it, but you mention this only happens from time to time.
Are you certain the STOP order has been successfully placed?
Are you connected to user data stream to see if you can get some events related to that order?

1 Like

The problem has been resolved. It’s not server side. As a result of changes in filters and an unsuccessful solution in the code, this bug appeared.