How to handle 'timeseries request failed'

igorg · August 2020

Hello,

this is the third problem I've got after Eikon was upgraded to 4.0.52 and Eikon Python module to 1.1.4.

[2020-08-20 19:02:19,799;s] - [DEBUG] - [send_json_request] - Request:{'Entity': {'E': 'TimeSeries', 'W': {'rics': ['AAPL.MX'], 'fields': ['VOLUME;VALUE;', 'TIMESTAMP'], 'interval': 'tick', 'startdate': '2020-08-20T20:00:00', 'enddate': '2020-08-20T20:10:00'}}}
[2020-08-20 19:02:19,800;s] - [DEBUG] - [log] - Request to http://localhost:9060/api/v1/data
   headers = {'Content-Type': 'application/json', 'x-tr-applicationid': 'xxxxxxxx', 'Authorization': 'Bearer xxxxxxxxxxxxxxxx', 'Content-Length': '191'}
   params = None
[2020-08-20 19:02:19,893;s] - [DEBUG] - [send_json_request] - HTTP Response code: 200
[2020-08-20 19:02:19,894;s] - [DEBUG] - [send_json_request] - HTTP Response: {"timeseriesData":[{"dataPoints":null,"errorCode":"TSIError","errorMessage":"Error: TSIRequestFailed, ErrorCode: TA-TSIRequestFailed, Fault: TSIError, Description: TimeSeries request failed","ric":"AAPL.MX","statusCode":"Error"}]}
[2020-08-20 19:02:19,894;s] - [WARNING] - [get_timeseries] - Error with AAPL.MX: TimeSeries request failed
[2020-08-20 19:02:19,894;s] - [ERROR] - [get_timeseries] - AAPL.MX: TimeSeries request failed |

I didn't see this error before the upgrade. How should we handle it? The logic re-tried 5 times and gave up. But when I re-ran the script 2 mins later, everything went fine.

What's the meaning of this error? Description is very generic.

Thanks,

chavalit-jintamalit · August 2020

Hi @igorg

I tested both send_json_request and get_timeseries functions

And both of them returned "no data available" error.

igorg · August 2020

https://community.developers.refinitiv.com/discussion/comment/64840#Comment_64840

Hi.

How should I use this information? And how does it answer my question?

Thanks

chavalit-jintamalit · August 2020

https://community.developers.refinitiv.com/discussion/comment/64847#Comment_64847

Hi @igorg

Because you mentioned that it works fine.

So I tested the api call with the same parameters with you.

It does not work for me, so I want to cross-check with you whether it works fine for you sometime?

igorg · August 2020

https://community.developers.refinitiv.com/discussion/comment/64856#Comment_64856

Please check my original post. It failed 5 times. Then in 2 minutes it began to work fine.

My questions are:

1. what does this error mean?

2. what can I do to avoid this error since it's temporary error and I cannot simply ignore it. It may lead to missed data during the collection

chavalit-jintamalit · August 2020

https://community.developers.refinitiv.com/discussion/comment/64857#Comment_64857

Hi @igorg

1. what does this error mean?

It is an error generated from the backend component.

There is no documentation about it.

The general suggestion would be to wait for some period and retry it again.

(I understand that this is not an ideal solution)

2. what can I do to avoid this error since it's temporary error and I cannot simply ignore it. It may lead to missed data during the collection

Does your application submit a lot of requests to the backend?

Do you think the application exceeds the limitation from https://developers.refinitiv.com/eikon-apis/eikon-data-api/docs?content=49692&type=documentation_item ?

igorg · August 2020

https://community.developers.refinitiv.com/discussion/comment/64859#Comment_64859

For all unknown errors like this one , we use the same approach - wait and re-try 5 times. It failed. Since this script is a part of bigger automated process, it caused the whole process to fail. And this is bad.

Second, I know about python api limits. When we hit this limit there is a special error returned (from the top of my head it's ERROR 429). In this case we pause the process and continue later. So it was not related to the limits.

My overall disappointment is after the latest Eikon upgrade I've got 4 different issues in production. And there is no way to roll it back.