DSS .NET API System.TimeoutException: Extraction took too long
I have a piece of code that creates a new instrument list, imports a new report template and creates an EOD schedule. All of this works each day @ 6:30PM EST.
The program then runs "WaitForNextExtraction" using the previously created EOD schedule and is set for "19:50" as the TimeOut. The poll seconds was set to 10 seconds.
The amount of data is quite small. The program would get to 19:50 EST and throw this error:
2023-06-29 19:50:01 [FTL]
System.TimeoutException: Extraction took too long
I have checked the Refinitiv DSS Website and the Extraction was completed but the program is not picking it up anymore. This all use to work and it started failing since: 06/12/2023, the last working extraction through the .NET program was 06/09/2023. No code was changed in the .NET program.
Best Answer
-
Hello @christopher.gentle,
The time taken by DSS servers to process a query depends on the query itself as well as the load on the server at that instance. It is possible that load on the server has changed and the time needed to process your query has gone up. I would recommend that you increase the timeout even more to account for these variables.
Also, the poll time of 10 seconds is quite short; for queries like EOD prices a minute should be fine.
0
Answers
-
Thanks for replying, I have changed the timeout to 60 seconds and will try that tonight and report back tomorrow.
0 -
I changed the poll seconds to 90.
The timeout is set for 7:45PM EST + 5 minutes (converted to UTC).
The extraction completed in on the DSS Web.
Last Execution:
07/04/2023 19:45:07I am still receiving the same error.
2023-07-04 19:50:32 [FTL]
System.TimeoutException: Extraction took too long
at DataScope.Select.Api.Extractions.ScheduleOperationsExtensions.WaitForNextExtraction(IScheduleOperations this, Schedule schedule, Int32 pollSeconds, TimeSpan timeOut)
0 -
Hi @christopher.gentle,
The 90 second poll interval does not affect the time in which your data is ready. Your app should wait much longer then 5 minutes to get the data.
You can raise a ticket at my.refinitiv.com to talk to DSS product team. They can advise on the timeout period for various extraction requests.
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 中文论坛