Lightstreamer TRADE message behaviour

[Tipper258]

Folks, back at the API after a few years away .... in the demo account, when an order is placed, I would expect to see CONFIRM and WOU messages. Instead no CONFIRM, only OPU messages. This is for orders raised on the web platform (trying to understand behaviours before coding order / position mgmt). 

Can anyone confirm, or have a blog post anywhere on what messaging is generated in the stream for order and position lifecycle please? i.e. when an order is confirmed, order updates, conversion to a position, position updates, closing messages and so on.

TIA, Alan

[jlz]

Hi, regardless of what anyone else might say on a blog if you are subscribed to the trading messages stream you should see confirmations of your trades. We have had other users in the forum pointing the same problem. The problem was always related to the demo account. Looking at what others have said I think that the demo account sometimes is not reliable regarding these messages. I never saw anyone complaining about the live account. 

 

[Tipper258]

2 hours ago, jlz said:

Hi, regardless of what anyone else might say on a blog if you are subscribed to the trading messages stream you should see confirmations of your trades. We have had other users in the forum pointing the same problem. The problem was always related to the demo account. Looking at what others have said I think that the demo account sometimes is not reliable regarding these messages. I never saw anyone complaining about the live account. 

 

Hi, thanks for this, I'm guessing that the API reference is what I should expect to happen, although testing assumptions before having to test with real money would have been nice. If anyone has examples of the CONFIRM, WOU, and OPU messages involved for a trade flowing through I'd be very grateful.

[Tipper258]

How does one file a bug in the API behaviour please, when it's not as per the documentation?

"tested" this in production and it's the same behaviour, messages that have the structure of a WOU are being published as OPUs, as well as real OPUs.

To work around you have to test for presence or absence of various properties in the json structure to derive which message type it's supposed to be.