ATE marked for later

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	-	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00	9:00 – 18:00
-	-	-	-	-	-	-

Supporter timezone: America/Lima (GMT-05:00)

Tagged: Known issue

This topic contains 38 replies, has 0 voices.

Last updated by Andreas W. 2 months, 1 week ago.

Assisted by: Andreas W..

Author	Posts
May 14, 2026 at 5:39 pm #18036741
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	The errata says: In some translations jobs in the Advanced Translation Editor (ATE), certain segments appear as “Flagged for later” even though the translator did not mark them manually. When this happens, these flagged segments prevent the translation job from being marked as complete, leaving the page in a pending or partially translated state. Source: https://wpml.org/errata/ate-some-segments-are-automatically-marked-as-flagged-for-later/ Anything further is more of a topic for the ATE-Development Team. So far, it looks like the issue is related to translation memory suggestions inside the translation system. I am afraid that I can not provide more details about the cause of the issue. There are two open development tasks on this matter that are still in progress.
June 2, 2026 at 12:50 pm #18075677
John-Pierre Cornelissen	Hi Andreas, Sorry this took much longer then expected. I have another site now where some sentences are "marked for later". But this might be a special/different situation. I translated this new site: hidden link I checked a few pages and then saw that the 'character in the name "San Mario's" was not translated correctly, it showed (I think) the unicode on the front end. I didn't pay proper attention to "marked for later" items at that time. I though the easiest fix was to add the name to the glossary, I did not check "Preserve related Translation Memory entries" (because they had a wrong character) and after adding, I clicked the [Update Translations] button. On the front end everything looked fine, but when went into the ATE, I saw that many sentences had the "marked for later" flag. All these sentences have the glossary term I added. There are also many sentences with that term that don't have that mark though. It could be that the "marked for later" flags on the site for which I opened this ticket also originate from the glossary, because that site already had many glossary terms before I started translation (from the original before redesign site). Is this something you want to have a look at? Thanks JP
June 2, 2026 at 3:53 pm #18076483
Andreas W. Supporter	We are really sorry about the inconvenience! The issue you are experiencing is a very complicated task that depends on various development tasks. Many of those tasks are already completed, but it will still take some time until this issue is finally solved in an upcoming ATE update. If there is anything we can do for you to compensate you, for example, credits for automatic translation, then please let us know.
June 2, 2026 at 4:11 pm #18076560
John-Pierre Cornelissen	Hi, I don't see this as a major issue, I only reported it because it happens with almost every new site and I was wondering why. But credits are always nice 😉 So you don't need a closed look in this one? Because then I am going to fix them. thanks JP
June 3, 2026 at 6:35 am #18077346
Andreas W. Supporter	Indeed, we all hope this issue will be fixed as soon as possible. I have forwarded your information regarding glossary entries to the devs for further revision and credited your site hidden link with 50k credits as compensation. One question: Do you also see that segments that are marked for later have the translated segments overwritten with the original content?
June 3, 2026 at 9:01 am #18077876
John-Pierre Cornelissen	Thank you! No these marked segments are still translated. What I did see though is that as soon as I went into the ATE, the translation of some segments was completely removed. Sometimes a short segment and sometimes a pretty long paragraph. On the front end these segments were still translated, but in the ATE they were blank and I had to click the translate button again. I am going to bring this site live today. Do you need me to keep this development or can I remove it?
June 3, 2026 at 1:08 pm #18078869
Andreas W. Supporter	For now, please continue. I would suggest we wait until the developers have completed all tasks on this matter first, and then we continue from there, if needed.
June 3, 2026 at 1:19 pm #18078918
John-Pierre Cornelissen	What do you mean with continue? Keep or remove my development site?
June 4, 2026 at 3:33 am #18079877
Andreas W. Supporter	Sorry for the misunderstanding! If you no longer need the development site, feel free to remove it. At the moment, the reported issue still depends on at least 2 open development tasks, and the ATE-Team is still working on solving this problem.