Is there something going on with the Eikon python api or server?
Upgrade from Eikon -> Workspace. Learn about programming differences.
For a deeper look into our Eikon Data API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
Is there something going on with the Eikon python api or server?
Hello @Market_Risk,
Thank you for your participation in the forum.
Is the reply below satisfactory in resolving your query? If yes please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.
Thanks,
-AHS
Hi,
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
I don't think a new app key is what resolved the problem.
Fiddler by default captures all HTTP requests going on the wire from your machine. If you start experiencing the issue again, you need to find the specific request that corresponds to the get_data call that didn't return. In your case you're looking for POST requests to https://amers1.apps.cp.thomsonreuters.com/Apps/UDF/MSF. Using the inspectors tab in Fiddler you can view the JSON body of the request and compare the payload to the argument values of the get_data method to match get_data call to the HTTP request.
Update: The "Request Timeout" error message is being received AFTER the function is manually cancelled. Until this occurs, the eikon api returns no response which causes the code to run infinitely as it is waiting on a response from the api.
Solution: Step 1) Run a eikon system test and see if Data Retrieval tests fail.
Step 2) If step 1 tests fail, clear cache.
Step 3) Problem should be solved. Re-run function and be happy.
The best way to troubleshoot the issue you described is to use Fiddler to capture the HTTP request corresponding to the get_data call that does not return. Fiddler will tell you the status of the HTTP request. With that information we can then see where the problem is: whether it's on the backend or the front end (or both).