Eikon Data Api. Timeseries request failed

2019-02-21 16:17:44,173 -- pyeikon -- DEBUG -- Request:{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['AAPL.MX'], 'fields': ['VOLUME;VALUE;', 'TIMESTAMP'], 'interval': 'tick', 'startdate': '2019-02-21T21:00:00', 'enddate': '2019-02-21T21:10:00'}}, 'ID': '123'} 
2019-02-21 16:17:45,282 -- pyeikon -- DEBUG -- HTTP Response code: 200 
2019-02-21 16:17:45,282 -- pyeikon -- DEBUG -- HTTP Response: {"timeseriesData":[{"dataPoints":null,"errorCode":"TSIError","errorMessage":"Error: TSIRequestFailed, ErrorCode: TA-TSIRequestFailed, Fault: TSIError, Description: TimeSeries request failed","ric":"AAPL.MX","statusCode":"Error"}]} 
2019-02-21 16:17:45,283 -- pyeikon -- WARNING -- Error with AAPL.MX: TimeSeries request failed

I've never seen this error before. I've got hundreds of this error and after some point it started to work again. I cannot reproduce it, but I have a log file from python module.

What does this error mean?

What should I do if I get this error? Re-sending the same request didn't help.

Find more posts tagged with

python

eikon

time-series

workspace

eikon-data-api

refinitiv-dataplatform-eikon

workspace-data-api

Accepted answers

Alex Putkov.1

This means the timeseries Web service tried to fetch the data from the timeseries database and failed. The error occurred at the headend and from the client side there's no way to tell what may have caused it.

All comments

Understood. Thanks

Similar behavior today:

2019-02-25 16:18:59,732 -- pyeikon -- DEBUG -- HTTP Response: {"timeseriesData":[{"dataPoints":null,"errorCode":"TSIError","errorMessage":"Error: TSIRequestFailed, ErrorCode: TA-TSIRequestFailed, Fault: TSIError, Description: TimeSeries request failed","ric":"BG.MX","statusCode":"Error"}]} 2019-02-25 16:18:59,733 -- pyeikon -- WARNING -- Error with BG.MX: TimeSeries request failed 2019-02-25 16:18:59,733 -- pyeikon -- ERROR -- BG.MX: TimeSeries request failed | 2019-02-25 16:18:59,757 -- pyeikon -- DEBUG -- Request:{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['BG.MX'], 'fields': ['VOLUME;VALUE;', 'TIMESTAMP'], 'interval': 'tick', 'startdate': '2019-02-25T21:00:00', 'enddate': '2019-02-25T21:10:00'}}, 'ID': '123'} 2019-02-25 16:19:00,110 -- pyeikon -- DEBUG -- HTTP Response code: 200 2019-02-25 16:19:00,110 -- pyeikon -- DEBUG -- HTTP Response: {"timeseriesData":[{"dataPoints":null,"errorCode":"TSIError","errorMessage":"Error: TSINoDataAvailable, ErrorCode: TA-TSINoDataAvailable, Fault: TSIError, Description: No data available for the requested date range","ric":"BG.MX","statusCode":"Error"}]} 2019-02-25 16:19:00,111 -- pyeikon -- WARNING -- Error with BG.MX: No data available for the requested date range 2019-02-25 16:19:00,111 -- pyeikon -- ERROR -- BG.MX: No data available for the requested date range |

Hundreds errors "TimeSeries request failed", then started to work normally. As you can see last 2 requests - 1st failed, second went through.

Again, cannot reproduce.

igorg

We are still experiencing the same problem with python:

2019-02-26 16:16:31,067 -- pyeikon -- DEBUG -- HTTP Response code: 200 


2019-02-26 16:16:31,067 -- pyeikon -- DEBUG -- HTTP Response: {"timeseriesData":[{"dataPoints":null,"errorCode":"TSIError","errorMessage":"Error: TSIRequestFailed, ErrorCode: TA-TSIRequestFailed, Fault: TSIError, Description: TimeSeries request failed","ric":"AC.MX","statusCode":"Error"}]} 


2019-02-26 16:16:31,067 -- pyeikon -- WARNING -- Error with AC.MX: TimeSeries request failed 


2019-02-26 16:16:31,067 -- pyeikon -- ERROR -- AC.MX: TimeSeries request failed |  


2019-02-26 16:16:31,087 -- pyeikon -- DEBUG -- Request:{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['AC.MX'], 'fields': ['VOLUME;VALUE;', 'TIMESTAMP'], 'interval': 'tick', 'startdate': '2019-02-26T21:00:00', 'enddate': '2019-02-26T21:10:00'}}, 'ID': '123'}

sdittmar

Why is the Web Service not passing this error on as part of the two documented exceptions: `Exception` or `ValueError` even though the error is printed to the console? It is unfortunate, that this error only shows up inside the raw request content. That makes it difficult to handle the error...

EXPLORE OUR SITES