This thread is resolved. Here is a description of the problem and solution.
Problem:
The client was experiencing persistent failures in WPML Advanced Translation Editor (ATE) with several automatic translation jobs failing due to a DownloadError. The error message indicated that the uploaded xliff file didn't belong to the system. This issue persisted even after attempting to resend the jobs.
Solution:
We identified that the issue was related to a site migration, where the translation jobs were created on a different domain and were not delivered properly. We resolved the issue by marking the affected translation jobs as delivered in our system. We also recommended the client to clear the cache in WPML, synchronize local job IDs with ATE jobs, refresh license data, and remove all messages and notifications through the 'WPML > Support > Troubleshooting' section. If the problem persists, we advised checking the Translation Dashboard again and contacting us for further assistance.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.
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.
Tagged: ATE
This topic contains 7 replies, has 1 voice.
Last updated by nodiraK 2 months, 1 week ago.
Assisted by: Prosenjit Barman.
| Author | Posts |
|---|---|
| February 13, 2026 at 11:39 am #17820222 | |
|
nodiraK |
We are experiencing persistent failures in WPML Advanced Translation Editor (ATE). In the WPML Translation Dashboard, several automatic translation jobs fail with the following error: Error type: DownloadError Message: The uploaded xliff file doesn't belong to this system ATE Job IDs: 112810633, 112810634, 112810635, 112810636 The errors occur when WPML tries to download translated content from ATE. Site details: Website: samarali.com Platform: WordPress + WooCommerce Translation method: WPML Advanced Translation Editor What we suspect: Possible desynchronization between site and ATE Orphaned / corrupted translation jobs Site key or domain mismatch Issue caused by previous updates, restores, or content changes What we need help with: Identify the root cause of the XLIFF ownership error Safely clean up or reset the affected translation jobs Restore normal operation of automatic translations Guidance if re-sending jobs or re-linking ATE is required Please let us know what diagnostic steps or actions you recommend. Job ID: 669 Job ID: 670 Job ID: 671 Job ID: 672 |
| February 13, 2026 at 11:43 am #17820244 | |
|
nodiraK |
Resend was attempted, but all jobs failed again. Message shown: ATE Job IDs: It looks like these jobs are orphaned or desynchronized. |
| February 13, 2026 at 1:09 pm #17820622 | |
|
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi there! Thanks for getting in touch with us. I'm Prosenjit from the WPML Development Team, and I'm here to help you get this sorted out. So I've taken a look at what's going on, and this is definitely connected to your site migration. Here's what happened: the translation jobs were originally created back when your site was at hidden link, but for some reason, those translations never got delivered properly. Now that you've moved everything over to samarali.com, ATE is trying to deliver them again, but it's getting confused because the URLs don't match up anymore. Basically, it can't figure out where the jobs were created versus where they need to go, which is why you're seeing that error. Since those translation jobs were created quite a while ago, I've gone ahead and marked them as delivered in our system. You shouldn't be seeing that error notice in your dashboard anymore. If you do still see it pop up, just run through these quick steps: - Go to "WPML > Support > Troubleshooting." Give it a check and let me know how it goes. I'm here if you need anything else! Best regards, |
| February 13, 2026 at 2:03 pm #17820950 | |
|
nodiraK |
Hi Prosenjit, Thanks for the explanation. I ran the Troubleshooting steps exactly as instructed: The error is still present. Also, I clicked “Discard jobs” for these items, refreshed the page (Ctrl+F5), but the same jobs still remain / reappear. Local Job IDs: 669, 670, 671, 672 Could you please permanently remove/close these orphan jobs and clear related notifications on the ATE/server side for our site? |
| February 14, 2026 at 7:08 am #17822248 | |
|
nodiraK |
Hi Prosenjit, We have verified that all affected pages and posts already have correct and published translations. So these 4 jobs are not needed anymore and can be safely removed. However: Local Job IDs: 669, 670, 671, 672 Since the translations already exist and are correct, please permanently delete / purge these orphan jobs and related notifications from the ATE/server side. We just need these 4 records fully removed from the system. |
| February 16, 2026 at 3:52 am #17824091 | |
|
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi There! I hope you're doing well. Sorry for the delay in responding due to the weekend. As I've updated the translation status to "delivered" in our system, this should take care of the issue. That said, I noticed you have object cache running on your site, and there's a chance it's still serving some older data from the cache. Could you try clearing all your caches and then check again to see if everything's working smoothly now? If you're still running into the same problem after clearing the caches, I'll need to dig a bit deeper to figure out what's actually going on. Would you mind sharing access to your site so I can take a proper look? I've enabled the private box for you, so you can securely share the login details there. Just so you know, all access information is completely secure – only our support team can see it, and once we've got everything sorted out and the issue resolved, you're free to remove that access anytime. Looking forward to hearing from you, and I'm here whenever you need me! Best regards, |
| February 17, 2026 at 4:54 am #17827430 | |
|
Prosenjit Barman WPML Supporter since 03/2023
Languages: English (English ) Timezone: Asia/Dhaka (GMT+06:00) |
Hi! Thank you for sharing the access information. I checked your site and fixed the issue. Please have a look. The list of unsolvable jobs was stored in the database. As mentioned earlier, those jobs were invalid because they were created from the staging domain. Since the translations were completed successfully, it was safe to remove them. I removed those entries from the database, and now the notice/error is no longer showing in the Translation Dashboard. Please check and let me know. I'll be happy to help if you need further assistance or clarification in this matter. Best regards, |
| February 17, 2026 at 7:34 am #17827874 | |
|
nodiraK |
Hi Prosenjit, Thank you for your help. I’ve checked the Translation Dashboard, and the 4 problematic jobs are no longer visible. The error notice has been completely removed. Everything looks good now. Thank you for resolving this. |
