Recommended code pattern for handling Eikon get_data timeout

Hi,
I'm a newbie to Eikon API
Is there a proscribed code pattern for handling timeouts? I have making a call to `get_data` in a loop: Each request takes about 10s to return but occasionally I get a Timeout (408/504).
I could just trap the timeout error and re-submit using following code as a starting point, but I just wondered is there an accepted/recommended code pattern to use?
thanks
e = None
try:
ek.get_data(instruments, fields)
except ek.EikonError as err:
e = err
# do I trap here and re-call get_data??
raise Exception(f'Eikon error {e.code}\n{e.args}\n{e.message}')
Best Answer
-
Hi @john.lupton
I would add a while loop with a success flag.
ric = ['PEUP.PA']
fields = ['TR.RetireDate']
isSuccess = False
while (not isSuccess):
try:
df,e = ek.get_data(ric, fields)
isSuccess = True
except ek.EikonError as err:
raise Exception(f'Eikon error {e.code}\n{e.args}\n{e.message}')
## the code here, already success in API call ##
print(df)If your API call requires 10 seconds, I can assume that you require a large amount of data.
Please try to split the universe or period to reduce the amount of the data in one API call.
This would raise the success rate of the API call.
0
Answers
-
@chavalit-jintamalit thank you for taking the time to respond. Could you clarify what do you mean by "split the universe" - I am asking for multiple fields across multiple RICs so do you mean reduce RICs or fields or both?
Thanks
0 -
Hi @john.lupton
For example:
If you request data for 2000 RIC, you may split the RIC to a smaller number.
If you request 20 RIC, but the data is 10 years of daily data, you may split the period into a smaller period.
If you request 10 RIC, but 1000 fields, you may split the field? or RIC? into a smaller list.
The point is to reduce the amount of data being transfer.
The bigger the amount of the data, the more chance that something may go wrong.
So try to balance it for your application.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 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
- 249 ETA
- 554 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
- 3 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.9K Refinitiv Data Platform
- 643 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
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛