ERROR: Job reported as Failed by data source

Hello,
I am unable to retrieve 5 days of quotations for the Eurodollar EDZ1 via a very simple request on DSS.
See the logs below.
What does mean : ERROR: Job reported as Failed by data source
Did I overlap the size limit for a file ?
I sent a message last week about the huge surge of volumes of data on Eurodollar contracts on CME.
It is difficult not to link the two things...
Thank you for your help.
Best
Extraction Services Version 13.1.41082 (6dbfc0caa311), Built Sep 18 2019 19:26:06
User ID: 9013496
Extraction ID: 2000000107047677
Schedule: ED9_20191021 (ID = 0x06d804e70ad10f8b)
Input List (1 items): ED9 (ID = 0x06d7a41ff1010e02) Created: 10/26/2019 17:46:14 Last Modified: 10/26/2019 17:46:23
Report Template (4 fields): Weekly_20191021_20191025 (ID = 0x06d74e08c8510d6e) Created: 10/25/2019 09:45:33 Last Modified: 10/25/2019 09:45:33
Schedule dispatched via message queue (0x06d804e70ae10f8b), Data source identifier (FA9A20E3A8E14D73A336919662CF5031)
Schedule Time: 10/27/2019 10:44:00
Processing started at 10/27/2019 10:44:14
Processing failed at 10/27/2019 13:43:36
Extraction finished at 10/27/2019 12:43:36 UTC, with servers: tm02n03
Instrument <RIC,EDZ1> expanded to 1 RIC: EDZ1.
Total instruments after instrument expansion = 1
Range Query from 2019-10-21T00:00:00.000 to 2019-10-25T23:59:59.000 (UTC)
ERROR: Job reported as Failed by data source
Best Answer
-
Hello @Jerome Guiot-Dorel
I have done some research for this error. Below is what I have found.
ERROR: Job reported as Failed by data source" message.
Investigations show we see some EURO instruments which are in IMM venue has been having abnormal high activities upstream causing the impact. Depending on the size of the date range and the instruments chosen, requests may be delayed and/or failed. The upstream team are planning a deployment for this coming weekend (26-27-Oct) that will help mitigate this issue. Until then, the client can try a small date range and if possible keep each request to a single day. Further analysis is underway.If you still found the error or have further questions, you can contact TRTH support via the case you have opened for this question.
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 725 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛