backend error: 500 internal server error - workaround

igorg

Last week we experienced a lot of "500 internal server error" during our standard data collection procedure. I see there are other posts regarding this error on the forum. So it seems like there were the issues with the TR data server(s).

I'm wondering if there is any workaround for this type of errors.. maybe it's possible to switch to some other/backup server until the error's fixed? maybe there is some configuration in Eikon app that allows to change the server?

Thanks,

Igor

Christiaan Meihsl

Repost of Zhenya's comment to close this query:

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.

Zhenya Kovalyov

@igorg while we are investigating the root cause of the issue there is no current workaround that I can recommend.

igorg

Please post some results of your investigation (when get some).

Thank you

wasin.w

Hi @Zhenya Kovalyov

Do you have any updates?

Zhenya Kovalyov

cross-post from a similar question for continuity purposes:

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.