What's the best practice to deal with "**F10: Service Down" status in Refinitiv Real-time Websocket
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.
Best Answer
-
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.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛