getting error code 500 today with get_timeseries request
@9029ef3d-816c-4b3d-b8a4-7e45f818c246 could you show your request please?
@Zhenya Kovalyov I can confirm the problems with time series requests. We're having the same issue. Error 500 in 50% of the requests. We ran these requests every day and had no issue. Sometime to run the save request multiply times helps, sometimes does not.
@9029ef3d-816c-4b3d-b8a4-7e45f818c246, @igorg
Are you still experiencing this issue? If not, could you please accept the response by @Zhenya Kovalyov. If you're still experiencing the problem, please let us know by responding on this thread.
Thanks.
@9029ef3d-816c-4b3d-b8a4-7e45f818c246, @igorg it appears that the underlying service feeding the time series data suffered from a high load of requests.
Should you experience this again, the workaround is to repeat the requests with a smaller set of data.
@9029ef3d-816c-4b3d-b8a4-7e45f818c246, @igorg many thanks for reporting this, we are looking into it.
This error means there is a problem on the server side. A Server Error can be caused by any number of things from uploading the incorrect file to as bug in a piece of code. This error response is a generic "catch-all" response. The web server is telling you that something went wrong, but it's not sure exactly what that is. If you have root access, you should review your web server's error logs to get more information about this. If you are using shared hosting plan, you should contact your host to get more information. The best way to debug the error depends upon the server and what's actually running at the time. Consider some debugging tips to help diagnose and fix common causes of this problem.
Why does changing Time Zone with get_timeseries() change the number of returned outputs
most robust.....get_timeseries or get_data for historic price series?
Retrieving historical minute-by-minute VWAP values
get_timeseries : Chain RIC closing yields
How can I retrieve all the Hourly data in RIC Future Continuation Expiry TRDEBFVDc1