Intraday Summaries Extraction Request fails with 500 Error code
I'm trying to extract tick data with a summary interval of 1 minute for one complete day by setting "QueryStartDate" and "QueryEndDate" in the "Condition" of my Extraction Request appropriately.
A perl script is scheduled to run everyday at 7 pm to get previous day's data. It worked without any problems until recently. But now, it keeps polling the server until it gets a HTTP 200 response for very a long time (around 1 hour) and eventually fails with a response code of 500 and message "Server closed connection without sending any data back".
If I re-run the script again next day manually, sometimes it works and sometimes it fails again with the same response code. I'm not sure why this is happening as the failure seems to be completely random or maybe depends on the time of the day at which extraction request is being performed.
Below is the Extraction Request. Any help regarding this would be greatly appreciated. Thanks!
{
"ExtractionRequest" : {
"@odata.type" : "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryIntradaySummariesExtractionRequest",
"ContentFieldNames" : [
"Close Ask",
"Close Bid",
"High",
"High Ask",
"High Bid",
"Last",
"Low",
"Low Ask",
"Low Bid",
"No. Asks",
"No. Bids",
"No. Trades",
"Open",
"Open Ask",
"Open Bid",
"Volume"
],
"IdentifierList" : {
"@odata.type" : "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers" : [
{
"IdentifierType" : "Ric",
"Identifier" : "FBTSZ7"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FGBSZ7"
},
{
"Identifier" : "FBTPZ7",
"IdentifierType" : "Ric"
},
{
"Identifier" : "FBONZ7",
"IdentifierType" : "Ric"
},
{
"Identifier" : "FOATZ7",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FGBMZ7"
},
{
"Identifier" : "FGBLZ7",
"IdentifierType" : "Ric"
},
{
"Identifier" : "FGBXZ7",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FLGZ7"
},
{
"Identifier" : "TYZ7",
"IdentifierType" : "Ric"
},
{
"Identifier" : "USZ7",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "AULZ7"
},
{
"Identifier" : "FVZ7",
"IdentifierType" : "Ric"
},
{
"Identifier" : "TUZ7",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FBTSH8"
},
{
"Identifier" : "FGBSH8",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FBTPH8"
},
{
"Identifier" : "KOAH8",
"IdentifierType" : "Ric"
},
{
"Identifier" : "FOATH8",
"IdentifierType" : "Ric"
},
{
"Identifier" : "FGBMH8",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FGBLH8"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FGBXH8"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FLGH8"
},
{
"IdentifierType" : "Ric",
"Identifier" : "TYH8"
},
{
"IdentifierType" : "Ric",
"Identifier" : "USH8"
},
{
"Identifier" : "AULH8",
"IdentifierType" : "Ric"
},
{
"IdentifierType" : "Ric",
"Identifier" : "FVH8"
},
{
"IdentifierType" : "Ric",
"Identifier" : "TUH8"
}
],
"ValidationOptions" : {
"AllowHistoricalInstruments" : 1
},
"UseUserPreferencesForValidationOptions" : 0
},
"Condition" : {
"MessageTimeStampIn" : "LocalExchangeTime",
"ReportDateRangeType" : "Range",
"QueryStartDate" : "2017-10-20T00:00:00Z",
"QueryEndDate" : "2017-10-21T00:00:00Z",
"SummaryInterval" : "OneMinute",
"TimebarPersistence" : 1,
"DisplaySourceRIC" : 1
}
}
}
It fails with this error message roughly after an hour
HTTP GET error code: 500
HTTP GET error message: Server closed connection without sending any data back
Best Answer
-
HTTP Status Code 500 is an internal server error indicating that the server encountered an unexpected condition which prevented it from fulfilling the request.
On Tuesday and Wednesday, there was a problem on the server, as shown in the alert.
Subject: Thomson Reuters Tick History version 2.0 - Custom Extractions - Disrupted
Problem Description:
Thomson Reuters Tick History version 2.0 Custom Extractions are disrupted.
This is due to an issue at Thomson Reuters and affects customers globally.
The major incident management process has been invoked at Thomson Reuters to aid service restoration.
Affected Report Templates: Tick History Time and Sales, Tick History Market Depth, Tick History Intraday Summaries and Tick History RawCurrently, the problem has been resolved. If you still see the issue, please let us know.
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
- 687 Datastream
- 1.4K DSS
- 622 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 680 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛