For a deeper look into our Elektron API, look into:

Overview |  Quickstart |  Documentation |  Downloads |  Tutorials |  Articles

question

Upvotes
Accepted
5 1 2 3

What's the best practice to deal with "**F10: Service Down" status in Refinitiv Real-time Websocket API?

Hi,


We are subscribing fixed income tickers from Refinitiv Real-time Optimized - Websocket RDP API. Occasionally our program receives messages like this:

[{"ID":7,"Type":"Status","Key":{"Service":"ELEKTRON_DD","Name":"EURAB3E30Y="},"State":{"Stream":"Open","Data":"Suspect","Text":"**F10: Service Down"}},{"ID":145,"Type":"Status","
Key":{"Service":"ELEKTRON_DD","Name":"CHFAB6L3Y="},"State":{"Stream":"Open","Data":"Suspect","Text":"**F10: Service Down"}},{"ID":153,"Type":"Status","Key":{"Service":"ELEKTRON_DD","Name":"CHFAB6L4Y="
},"State":{"Stream":"Open","Data":"Suspect","Text":"**F10: Service Down"}},{"ID":383,"Type":"Status","Key":{"Service":"ELEKTRON_DD","Name":"JPYSB6L20Y="},"State":{"Stream":"Open","Data":"Suspect","Tex
t":"**F10: Service Down"}},{"ID":326,"Type":"Status","Key":{"Service":"ELEKTRON_DD","Name":"USDSB3L7Y="},"State":{"Stream":"Open","Data":"Suspect","Text":"**F10: Service Down"}},{"ID":106,"Type":"Stat
us","Key":{"Service":"ELEKTRON_DD","Name":"USDSB3L30Y="},"State":{"Stream":"Open","Data":"Suspect","Text":"**F10: Service Down"}}]

We are wondering what the best practice to deal with it is. Currently we disconnect and reconnects, re-sending the login request but it always fail with:

[{"ID":1,"Type":"Status","Domain":"Login","Key":{"Name":"..."},
"State":{"Stream":"Closed","Data":"Suspect","Code":"UsageError","Text":"Login rejected. Already pending login."}}]

and only succeeds after ~20 min.

refinitiv-realtimerefinitiv-data-platformwebsockets
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

Upvotes
Accepted
17.5k 34 12 12

Hello @bhansen

The "Stream":"Open","Data":"Suspect","Text":"**F10: Service Down" status message means the item stream is opened, but the data is not available because the "ELEKTRON_DD" service on the RTO server-side is down.

Basically, the WebSocket server automatically recovers the item subscription for the application when the service is up again.

However, I recommend you contact the RTO server support team if you continue encountering this "Service Down" issue. You can submit a ticket to the team via the https://my.refinitiv.com/content/mytr/en/productsupport.html page.

rrto-ticket.png


rrto-ticket.png (22.1 KiB)
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.