Hi @pierotofy,
Do you have an issue with the service today? Today we have 502 responses after roughly 30 sec (while we had 520 after roughly 50 sec yesterday). This means the server doesn’t have time to perform the queries on our longest content to translate, which doesn’t contain more than 3000 characters before the encoding made by httr::build_url() in R. We did 3000 characters chunks as a way to get close the 5000 limitation, while minimizing the chance of busting it.
In the screen shot below, you can see the timestamp of the log, what is important to notice is the status code and the Time elapsed.
Another issue here, we have a 502 with a content of 570 char to translate.
[ 2022-07-21 11:36:15 ] : Result request row name 391 with nchar = 570 is : Status_code: 502 Time elepased : 30.4199368953705
This is very concerning as I expect to use this service that I have paid for much more than I currently have in the next weeks.
Thanks for addressing this.