Price streaming using platform session showing inconsistent behaviour

RakanK

Application: AlphaDesk connecting via Refinitiv Data .Net Library using a PlatformSession
Issue: Subscribing to the same set of ticker/fields is showing inconsistent behaviour. One of the following 3 scenarios occur (in likelihood order):

1. Streams for pricing are successfully connected and receive refresh/updates
2. The price streaming seemingly stops working at some point during startup. Some prices were retrieved but don't refresh anymore
3. The connection disconnects and warns "Retrying in 15 seconds", after the 15 seconds it reconnects and prices are retrieved and update

The largest concern is regarding the second scenario as the application does not receive any price updates.

Notes:

• For scenario 2, the connection seems to die around the point where we're receiving "access denied" msgs for some tickers - we resubscribe to the delayed ticker in these scenarios
• The session state continues to be Session.State.Opened

Attaching logs from the data library for scenarios 1 & 2

refinitivLib_norefresh.log

refinitivLib_success.log

cristian.baciuwahl

Hello Rakan,

Could you please send those 2 log files to cristian.baciuwahl@lseg.com ? Due to specific security constraints I am not allowed to open attachments from posts using my work machine.

Also, could you please provide some code samples in the comments so that we can investigate and attempt to recreate the possible issue?

Regarding your 3 scenarios:

1. I'm presuming this is the expected happy path - stream connects, refresh is followed by updates with no issues.
2. If you receive an "access denied" response, you might have to contact the Content teams to verify your machine account for any license issues preventing you from accessing that data. The library does not send any "access denied" messages/logs by itself, meaning these messages are coming from the backend. What happens with these instruments when you subscribe to them again?
3. The backend has decided to close the connection, but if the machine is still logged in into the session, the library will retry a couple of times to reconnect, while keeping the session open. The session is usually closed only when authentication fails or when the user explicitly closes it, so point 3 might be related to point 2, but not necessarily.

Best regards,

Baciu Wahl Cristian