RDP API stalling often: Is the whole Infrastructure broken since about last November??
Am I the only one??
Since about last November, I have random issues with RDP just simply stalling.
The help I get from LSEG is also ... stalling, evasive, asking for all sorts of information then saying it is fixed, but it isn't.
"Good day! I trust this email finds you well.
This is [], Technical Specialist and I am going to assist you from here while Josh is not available.
Regarding your questions this issue is a limitation of Eikon API / UDF. Customers globally are impacted by this issue.
The necessary changes has been implemented by our Developers Team internally to make sure that it it will not happen again. We advised to send smaller requests (less amount of RICs per request) or move to RDP Refinitiv Data Platform.
Let me know if you have any other question. ..."
I suspect authentication issues and it mainly affects fundamental data and portfolio/watchlist content:
rd.content.fundamental_and_reference.Definition(universe=PORT],fields=FIELDS).get_data()
rd.content.fundamental_and_reference.Definition(universe=RICS, fields=FIELDS).get_data()
It is either working or not, no code changes here, no system changes, no changes from my side.
Totally unreliable.
Here are is a snippet from the LOG file
System tests in workspace are ok
This has costing me dozens of hours for the last few months.
Anybody having a smart idea except moving back to Bloomberg?
Thx
Best Answer
-
@the.swiss Thanks for your co-operation on this - there were some backend issues affecting performance recently. Thanks for highlighting in detail what was taking time and failing etc. After speaking to the team responsible for this service - we have implemented some changes on the server-side last week and performance and stability is greatly improved since then. I hope this has helped.
1
Answers
-
@the.swiss Hi - really sorry to hear of your issues - I am going to go through the tickets you have raised recently - I noticed @Jirapongse has also helped you previously on the code side on this Q&A portal. Please bear with me for a bit. I havent seen your code yet but are you using try-except blocks to catch server errors and then to represent that calls that are failing? Also may I know what time and timezone you are running these updates (ie is it a regular time or ad hoc)? Thanks in advance.
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 中文论坛