[Resolved] Segments becoming untranslated

Thank you for your detailed notes.

The translation memory is merged already.

I’d like to highlight an example I mentioned earlier from the jobs on the 30th and 31st of January:

- On the 30th, one of the affected segments was missing from the original content.

- On the 31st, the same segment exists again in the next job.

This pattern indicates that the original content was altered between jobs, or that a plugin was disabled while translations were being processed. When this happens, WPML treats the content as changed and resets the translation memory for those segments. That’s why they appear untranslated again, even though they were previously completed.

This is different from the known ATE behavior, where segments can be marked “Save for later.” In your case, the trigger seems to be content changes or plugin state changes during translation jobs.

Could you please confirm the current ATE ID for your site?

Go to WPML > Support > Troubleshooting > Your Automatic Translation account id is and provide me the current ID.

Further, it would be helpful if you could pass me all the permalinks for original content that currently shows issues on the Advanced Translation Editor. I will then review those jobs and try to assist you on this matter. We can make an exception here and compensate you with some credits to solve those issues, I just need to know how many credits might be needed.

Thank you for the provided details!

The problem seems to be that this site was not registered properly, and there were more organizations to be found than I expected earlier. The site moved various times between a WPML test site, a staging site, and a production site.

It further looks like, when you moved this site to the product on July 11 in 2025, the site was not migrated properly. It was moved instead of copied, which means the migration created a completely new entry on the system, instead of copying the existing translation memory to the new site.

Note that if you use various instances, you can connect the site to make them share their translation memory, glossary, and credits:
https://wpml.org/documentation/automatic-translation/automatic-translation-subscription-for-multiple-sites/

I have handled this now by manually merging the translation memory of all site organizations into the current one.

Please now cancel the affected "In Progress" jobs at WPML > Translation Dashboard > Jobs.

Then, create a new job for the affected contents at WPML > Translation Dashboard.

You can assign the translations to yourself and then access them at WPML > Translations.

I already did this now for "Best of Nightlife and Bars in La Spezia" and I can see a 100% completed translation on ATE.

Please verify if the issue is solved now, but take note that you need to create new translation jobs first. You might not see the changes on jobs that are currently in progress.