...et 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.