atsStatus-A23: Service has gone down. Will recall when service becomes available.

Hi,
We are using ETA Value Added API to fetch realtime data from TREP, but for our customer, everyday at 07:00 AM in morning, another team in the bank is restarting their system, and it caused error message "-A23: Service has gone down. Will recall when service becomes available".
What is the way to handle this through ETA? Will ETA take care of it? or we need to resubscribe to all the tickers using that service?
Please sugges, what is recommended way to handle this service.
Thanks
/Bhimrao
Best Answer
-
Thanks for reaching out to us.
You need to check the stream state of the subscribed item.
If the stream state is still Open, it means that the API or the infrastructure will perform a recovery on behalf of the application.
StatusMsg
streamId="5"
domain="MarketPrice Domain"
state="Open / Suspect / None / 'F9: Service has gone down. Will recall when service becomes available.'"
name="IBM.N"
serviceId="5001"
serviceName="ELEKTRON_DD"
StatusMsgEndHowever, if the stream state is Closed or Closed_Recover, the application needs to resubscribe to the item.
I hope that this information is of help.
0
Answers
-
Thanks0
-
Hi @Jirapongse,
We're seeing this issue as well, and it also happens when other applications on our network begin receiving elevated traffic (for us, our connection to the RTSDK for which we receive European market data suffers when the US markets open).
Do you know why this might be happening? Our application does recover, but it also loses data because of this. How can we configure our application to not be as sensitive to the traffic conditions of the network, if that's what's happening?
0 -
The questions with accepted answers are not monitored by forum moderators. To ask a new question, please start a new thread (Ask a question).
This message is sent from the infrastructure (RTDS) to indicate that the service is down and RTDS will perform item recovery. If the application retrieves this message, you need to contact the infrastructure team (RTDS support team) to verify what the problem is.
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.8K Refinitiv Data Platform
- 622 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 83 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛