Wrong order of websocket messages


This looks like a new bug, which introduced when the “reason” field added to the account_update message:

When an order fill, the account_update message comes first, and the order_update message comes second. This is the wrong order.

The right order is:
Order fill first (order_update message) and
Position created second (account_update message)

Could you fix this?

User data stream payloads are not guaranteed to be in order during heavy periods;
Please read the details here - https://binance-docs.github.io/apidocs/futures/en/#user-data-streams