I found a workaround that works for me. I changed the settings to classic translator, then went to translation management. I selected a translation stuck in "progress" and added it to the translation queue again (this will cancel any translation already in progress). this did the job. So it is 100% not an issue with some other plugin.
Sorry for the delay. I was unavailable for some time.
The workaround seems reasonable to me. Does that work for you? If you are still experiencing this problem, I will keep checking. In that case, I would need new access credentials, as the ones you shared no longer allow me access.
The workaround seems to be working for me so no further assistance is required. I do wonder though if there would be any future downsides of not using ATE. Will this way of doing things keep on working? It would still be nice to have it fixed in some future patch.
Including better support for Redis (other support question I posted long ago).
This is my server info (see attachment). It is a large host in Belgium (Combell).
I think it would indeed be good to fix it at the core as I found several others online with the same problem. I am however happy I found a workaround. I don't use automatic translations as we are required to know multiple languages ^^.
We need to investigate it further to find a suitable solution. Could you please share or reactivate the access so I can replicate the error, conduct further checks, and report to our team if necessary? Does the issue happen with a new product?
Would you mind using the copy you made for your tests? I have been working hard to clean up things here so I prefer to not change anything at this time.
