Discover Refinitiv
MyRefinitiv Refinitiv Perspectives Careers
Created with Sketch.
All APIs Questions & Answers  Register |  Login
Ask a question
  • Questions
  • Tags
  • Badges
  • Unanswered
Search:
  • Home /
  • Eikon COM /
avatar image
Question by davidk · Apr 24, 2019 at 04:19 PM · dex2eikon comfundamental dataeikon com api

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.

People who like this

0 Show 0
Comment
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Reply

  • Sort: 
avatar image
REFINITIV
Best Answer
Answer by Alex Putkov. · Apr 24, 2019 at 05:05 PM

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.

Comment

People who like this

0 Show 0 · Share
10 |1500 characters needed characters left characters exceeded
▼
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Watch this question

Add to watch list
Add to your watch list to receive emailed updates for this question. Too many emails? Change your settings >
8 People are following this question.

Related Questions

Dex2. Unexpected result for some RICs

Dex2 Interim Data

Exception while calling CreateRData on Dex2.RData

Dex2. Differences between Eikon and API returns for TickerSymbol, ExchangeTicker

Dex2Mgr instrument list and display parameters

  • Feedback
  • Copyright
  • Cookie Policy
  • Privacy Statement
  • Terms of Use
  • Careers
  • Anonymous
  • Sign in
  • Create
  • Ask a question
  • Spaces
  • Alpha
  • App Studio
  • Block Chain
  • Bot Platform
  • Calais
  • Connected Risk APIs
  • DSS
  • Data Fusion
  • Data Model Discovery
  • Datastream
  • Eikon COM
  • Eikon Data APIs
  • Elektron
    • EMA
    • ETA
    • WebSocket API
  • Legal One
  • Messenger Bot
  • Messenger Side by Side
  • ONESOURCE
    • Indirect Tax
  • Open PermID
    • Entity Search
  • Org ID
  • PAM
    • PAM - Logging
  • ProView
  • ProView Internal
  • Product Insight
  • Project Tracking
  • Refinitiv Data Platform
    • Refinitiv Data Platform Libraries
  • Rose's Space
  • Screening
    • Qual-ID API
    • Screening Deployed
    • Screening Online
    • World-Check One
    • World-Check One Zero Footprint
  • Side by Side Integration API
  • TR Knowledge Graph
  • TREP APIs
    • CAT
    • DACS Station
    • Open DACS
    • RFA
    • UPA
  • TREP Infrastructure
  • TRIT
  • TRKD
  • TRTH
  • Thomson One Smart
  • Transactions
    • REDI API
  • Velocity Analytics
  • Wealth Management Web Services
  • World-Check Data File
  • Explore
  • Tags
  • Questions
  • Badges