subscribeOrderUpdates sends incorrect events

[alexander-hagen]

Describe the bug
After succesful subscription to subscribeOrderUpdates, the socket sends incorrect event messages.

Expected message is:
{
"e": "executionReport",
"I": "209818131719847936",
"E": 1499405658658,
"u": 123456,
"s": "ETHBTC",
"c": "mUvoqJxFIILMdfAW5iGSOW",
"S": 1,
"o": 1,
"q": "1.00000000",
"p": "0.10264410",
"x": 1,
"X": 1,
"i": 4293153,
"l": "0.00000000",
"L": "0.00000000",
"n": "0",
"N": null,
"T": 1499405658657,
"t": -1,
"O": 1499405658657,
"z": "0.00000000",
"Y": "0.00000000",
"C": "test",
}

Actual message is:
{ event: 'user_order_update', status: 'ok', ts: 1707595498487 }

To Reproduce
Steps to reproduce the behavior:

1. Open a websocket with api keys and valid token
2. Once authenticated, 'subscribe to Order Updates'
3. See error

Expected behavior
After subscribing to Order Updates the correct response should be given

[alexander-hagen]

It might be that if there are no order updates, the event does not contain a payload. To validate this it needs a balance on the exchange to allow order creation.