optimal handling of DS_DE_NULL_ERROR
Sometimes when we get fundamental data via the Dex2 API, we get DS_DE_NULL_ERROR back, usually with either the text "Asynchronous Query library internal error" or "Server response is not valid." This happens seemingly at random, usually after at least a minute has passed-- possibly a timeout from upstream.
Usually when we get fundamental data we get it for our whole portfolio of 1,000 stocks (we're quants). In general when we receive the above messages our strategy has been to try to resend the request right away, usually breaking it into more, but smaller, requests. However, sometimes, that results in further errors, including "DS_DE_NULL_ERROR: Too many long-running requests were detected."
Is there a standard suggestion for what's the best way to package requests of data to the Eikon COM API? Is there an optimal time to wait after receiving a DS_DE_NULL_ERROR response before retrying the request? Is there an optimal size for an individual request to avoid timeouts in the first place? Any suggestions would be appreciated.
Best Answer
-
I'm afraid there's no such thing as an optimal size of the request. Or rather the optimal size can only be determined empirically and it will likely vary depending on the type of the request. Generally you want to avoid sending requests that take longer than a minute to process. It's better to break such requests into smaller ones by splitting either the instrument list or the fields list, or both. The error "Too many long-running requests were detected" is returned when the backend detects a number of requests from you taking more than 5 minutes each to process. When this happens the backend will stop process any requests from your Eikon account for a period of time.
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 中文论坛