Background of the issue:
I am trying to translate the entire website automatically from German into Polish and English. Most of the content has been translated manually already, but I want to switch to automatic translation for past and future content. I activated pay-as-you-go and the automatic translation. I have updated WPML, WordPress, and plugins to the latest versions, checked PHP and WP memory limits, verified language mapping for Polish, used WPML troubleshooting tools, switched translation mode, checked for conflicting plugins, and reviewed WPML error logs.
Symptoms:
The translation queue gets stuck. I see 'x items in queue' and 'posts are being prepared for translation', but there is no translated content or translated custom fields.
Questions:
Why is the translation queue getting stuck?
How can I ensure that automatic translation processes all content as expected?
unfortunately nothing has happened overnight. The content is "still being prepared" and not a single credit has been used. There is no new notice in the error log.
What should I expect? Should the message "still being prepared" disappear at some point?
We suspect a database corruption, or perhaps an issue occurred when you removed the Austrian language. We need to investigate this issue further on our servers. Please allow me to take a copy of your site. For this, I must install a plugin like Duplicator or All In One Migration. Please let me know if you agree.
thank you for the response. In order for that to proceed I will need a Data Processing Agreement since you will have a local copy of personal data like names and e-mail adresses. Can you provide something like that?
You can do it on a staging site, and then we will take a copy of it. Or you can do it yourself and share the copy without the data with us. You can upload it to a service like Google Drive or Dropbox and share the link with me. For this, I'll enable a private message for the following reply.
I still haven't received any information from our second-tier supporters regarding this case. I've sent them a message and asked them to get back to me regarding this matter. When it happens, I'll update you here.
Our second-tier supporter checked the copy of the site, but he couldn't see the problem there, as it is not an exact copy of hidden link. He could confirm this by inspecting the website ID and the ATE organization. Our second-tier supporter explained that the original site from which the package was generated (the pack you shared with us) was with website ID: 6d661886-42f1-4962-b9d6-c3917d7c0393 and organization unit ID 5a77c642-1f10-4454-9e70-082f80ae3a6f. Whereas the one with the ate job ID 145510078 (the job that caused the queue to be stuck) is 39616464-6439-5466-b130-323564356436 and organization unit ID cf20f096-83f7-4d9a-959e-a67e9cd640fe. So our second-tier supporter realized that he was not testing the same environment where the problem is. Access to your site is no longer working, so our second-tier supporter is unable to check it. Therefore, we must have a copy of hidden link where this problem occurs.
Could you please share it with us so we can investigate this issue further?