Unable to retrieve job details | Do not work translation editor

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing issues with WPML Automatic Translation where updating content in the primary language does not load for translation and shows the error message 'Unable to retrieve job details', this might be due to Gzip compression enabled on your server.
Solution:
We recommend asking your hosting support to disable Gzip compression. You can find more details on this issue in our errata page: Translation jobs not synchronised when Gzip compression is enabled. After disabling Gzip compression, restart your server. Once your site is up again, edit the original content, save the page, and try to translate it again. If the problem persists, please do not hesitate to contact us for further assistance.

Please note that this solution might be irrelevant if it's outdated or not applicable to your specific 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 continues, please open a new support ticket at WPML support forum.

100% of people find this useful.

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: Known issue

This topic contains 11 replies, has 0 voices.

Last updated by Andreas W. 4 months ago.

Assisted by: Andreas W..

Author	Posts
January 2, 2026 at 6:53 pm #17700944
danielS-274	Happy New Year, I’m still experiencing an issue with WPML Automatic Translation (ATE) on one of my websites — and unfortunately not only on one. The problem occurs when I update content in the primary language (Czech) and then switch to ATE. The content for translation does not load and I receive the error message: “Unable to retrieve job details.” We already discussed this issue in a previous support ticket with Andrej, who suggested that the problem was most likely related to the hosting. However, this does not seem to be the case. I have tested another website on a different setup, and everything works correctly there. Over the holidays I was offline, and only now noticed that the previous ticket was closed, so I am opening a new one. At the moment, I am facing this issue on three different websites, and it is significantly slowing down client updates. For the past six months, I have been forced to handle translations by manually editing translated pages, but I would like ATE to work as it did before — one click and automatic translation. I’ve already tried the steps mentioned in other Task history cases, but the issue persists. I can provide admin access so you can check the problem directly. This situation is becoming very frustrating, and client work is piling up because of it. I would really appreciate your assistance. Thank you in advance. Best regards, Daniel
January 2, 2026 at 7:54 pm #17700983
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, I see on our system that the error seems to occur on the page "WPML Test" but not on other pages. The issue might be related to the original content of this page. The XLIFF shows: The <body/> element is empty, so there is no translatable content (HTML or text) inside this file. Conclusion - HTML content in this file is empty Reason: This XLIFF file contains only metadata and a reference to the page, not the page’s HTML. There is nothing translatable found by the WPML Translation Editor inside this content. Workaround: Please make sure to add content to the page, save the original page and then test the translation again. If you have another example, please send me the permalink of the original affected page or post. Best regards Andreas
January 2, 2026 at 10:11 pm #17701051
danielS-274	Hi Andreas, may i get you access to website?
January 2, 2026 at 10:13 pm #17701052
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, I'd be happy to take a closer look at this and request temporary access (wp-admin and FTP) to the website to investigate the issue further. You'll find the necessary fields below the comment section if you log in to leave the next reply. The information you provide will be private, meaning only you and I will be able to see and access it. IMPORTANT Please be sure to create a backup of the website and database before granting us access. If you don't see the "wp-admin / FTP" fields, your login credentials for the post and website will be set to "PUBLIC." Do NOT publish the information unless you see the required wp-admin / FTP fields. The private reply form looks like this: hidden link When replying again, click "I still need assistance". Video: hidden link Please note that we are required to request this information individually on each ticket. We are not permitted to access any login information that was not specifically provided in the private reply form for this ticket. Best regards, Andreas
January 4, 2026 at 2:07 am #17701818
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Thank you for your patience! At the moment, it is unclear to me what causes this issue, as the site appears to be registered correctly in our system, and WPML's configuration in WordPress looks correct. I will be taking a local copy of the site for testing in a minimal setup. This way, I can test if a third plugin or the theme might be causing these unexpected issues. Once I am done with this test, I will reach out again. As I do not work on Sundays and Mondays, I will need to ask you kindly for some patience. What you could do in the meantime: - Take a complete backup of your site and database, or create a staging site for running the updates and testing - Switch to a default theme, and disable any plugin apart from WPML Multilingual CSM and WPML String Translation, then edit one of the affected pages, save it, and try to translate again. - Note that on my test, this issue seems to occur even when using Gutenberg (without Elementor) If the issue disappears, we know now that the theme or a third plugin is causing the issue, and we can run further tests. In this case, you would activate the disabled compenents one-by-one and after each step test if the issue occurs again. As soon as the issue occurs again, it is likely the last component (theme or plugin) that has been enabled. If the issue persists while testing with a default theme and only WPML Multilingual CMS and WPML String Translation, then we would need to investigate further.
January 6, 2026 at 10:55 am #17706312
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	On a local copy of your site, this issue does not occur, as shown in the attached screenshot. This suggests the problem is either related to your current server environment or your wpml.org account. Based on our observations, I would like to rule out first if the issue is on the server‑side. Could you please check with your hosting support whether the server’s firewall or security settings might be blocking connections to one or more of the following domains: wpml.org cdn.wpml.org api.wpml.org api.toolset.com cloudfront.net You can find more details in the official WPML documentation: https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/ If reaching out to the hosting support will not solve this issue, please let me know and we will take further steps.
January 8, 2026 at 2:37 pm #17713361
danielS-274	Hi Andreas, i have answer from hosting provider: "Of course, we don't block anything like that by default." regarding the account for the velvetmassage.cz domain at wpml. I did it twice and it seems to be fine in the administration. I did this before contacting wpml support. So that probably won't be it.
January 8, 2026 at 3:19 pm #17713477
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	As the issue does not occur on my local copy of the website running on a virtual server, I deduce that there might be an issue with your user account. I am escalating to the Second Tier Support for further revision, as my access to the accounts and translation system is limited in this case. As soon as I have feedback from the team, I will reach out to you again.
January 8, 2026 at 3:34 pm #17713580
danielS-274	ok, thank you.
January 8, 2026 at 4:01 pm #17713638
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Hello, We have a known issue that allows translation jobs not to sync correctly of Gzip compression is enabled in PHP on the server. Please ask your hosting support to disable Gzip compression. Errata: https://wpml.org/errata/translation-jobs-not-synchronised-when-gzip-compression-is-enabled/ The server will need to be restarted after making this change. Once the site is up again, edit the original content, save the page and try to translate it again. If this does not solve the issue, please let me know. Best regards Andreas
January 8, 2026 at 9:11 pm #17714404
danielS-274	Finaly! Its work! Thank you so much Andreas! We disable with hosting support Gzip. After i clear cache in wpml and turn off translation sites in Translation Dashboard> Translation Jobs. And after open problematic sites and all works!
January 9, 2026 at 11:53 am #17715865
Andreas W. WPML Supporter since 12/2018 Languages: English (English ) German (Deutsch ) Timezone: America/Lima (GMT-05:00)	Thank you for reaching out, and I am glad to hear that we were able to solve this issue. Let me know if there is anything else I can do for you 🙂