Background of the issue:
I working on a multisite network with a large amount of content and the client has activated auto translation of everything using PTC as the translation engine. Pay as you go is active.
Symptoms:
When I try to send items for translation, I receive the message: 'You don’t have enough credits to translate your content automatically.'
Questions:
Why am I receiving a message about not having enough credits when trying to translate content?
How can I resolve the issue of not having enough credits for automatic translation?
Hello, I'm Pieter's client. The site we were seeing the "not enough credits" error for was using Pay As You Go so I could not assign it any Prepaid Credits. So here's what I did:
Turned off Pay As You Go
Assigned 20,000 credits from the inactive sites to the problem site
Turned Pay As You Go back on
When I did this, I received an invoice for October and it seems as though my Pay As You Go counter has restarted. Please adjust my pay-as-you-go bill to reflect the maximum possible volume discount, since I had met that threshold already this month.
Translations have been running through the night, but the counter of what still needs translating keeps going up instead of down.
And just now the system has run into an error, screenshot attached.
The strange thing is that translations still seem to be continuing as the number under Translation Status now continues to increase...
To say that this system is non-transparent is a huge understatement!
Naturally I have clicked the "Fix now" button, which results in an overlay where absolutely nothing is happening, except the number under Translation Status still continues to increase...
So the ATC servers simply cannot handle a large load and to be honest I think that you have grossly underestimated that part of your service!
For the price your clients pay for auto translation, one should be able to expect speed and zero interruptions.
I have had to switch auto translation via PTC off and set it to new content only and I am now manually - yes, you read that correctly - manually adding content 200 at a time to the auto translation queue. More than 200 at a time your system also cannot seem to handle, so you can imagine that with more than 12,000 Posts this is going to take a while.
WPML needs to seriously re-think its offering, because for large content websites this simply is unacceptable!
Please note that our support team was offline during the weekend. We’ve reviewed your account with the ATE team and confirmed that your previous Pay As You Go subscription was canceled and a new one was activated.
Unfortunately, this reset the previously enabled limits, as each subscription comes with its own quota.
Note: On Friday, while reviewing your account, I also added some extra credits to help you move forward with your project.
Regarding the load, with Auto Translate Everything enabled, you should be able to translate your entire website without any issues or performance problems.
However, since this is a new Pay As You Go subscription, you might reach the credit limit again. If that happens, please contact us before deactivating the subscription so we can adjust your plan and increase the limit. (At the moment, I can see your account is correctly showing over 26M credits limit.)
For performance troubleshooting, please go to WPML → Support → ATE Error Logs and share the top 5 errors you see there. This will help us check if any errors are being triggered.
2025/10/15 12:35:01 AM XLIFF Server Communication No se pudo leer el archivo xliff. 187767 163091892 {"downloadUrl":"https:\/\/ate-production.s3proxy.wpml.org\/translated_xliffs\/xliffs\/115\/622\/963\/original\/translated_161819146_when_it_comes20251013-3909-145gxby.xliff20251013-16543-1n62e7v.xliff?Expires=1761093297&Signature=lvRgO1iG8Xldh-FTaFRKTUAwM06TsGGJaZoaZgasSqsWAljifKRhWwYua3zDkiqT1liYZL4uQrM0onIMg~S6FdVQc6kvjSW~Zizecq8FBkihdZK~9d1nLAJ0QtmNIkX8eTcWK-cf6vq845DMoxRIwj-PQFwlAC3PMrF3AqwMpfcqRY4q~F2Vso7SlwAWf2hg~A2aLk6HNu0o1BMj2gneBb7N8jLc6uqXjyONPoF5tFJHoukKhFw8fFOA~ZTz4RG6LiAMPNi0bqi-VFVQJDRsYN5CX4gOhVAHBKVyhnn5pqEHklP46LbVSJcmA9PlteuO8mkj0KCY9ncqw4~zGixfHQ__&Key-Pair-Id=K1C11UVRQNXLRQ"}
2025/10/15 12:35:00 AM XLIFF Server Communication No se pudo leer el archivo xliff. 187765 163091302 {"downloadUrl":"https:\/\/ate-production.s3proxy.wpml.org\/translated_xliffs\/xliffs\/115\/622\/743\/original\/translated_161818566_Confessions_of_an_Ex-Elder20251013-9804-1059w6k.xliff20251013-17022-1ftqz1e.xliff?Expires=1761093297&Signature=GhF1LgsmsnRVKnrAPi1-Loegjib2cHq4BVJ6avC2NWZVUvEFoMvNq3qfAE~E1SO7gFCV5SfmBD7hxWPuswbaI7Ifpa2jJmweBqxIoXtz1UzTQCfGWCWMBOjydCTCiXGm2phBUgzd3YIDrQ6llAswpqHN9PEp~l6ObMIpJg6~7VgMjGEuFy4O0ET0KqkPqNYShxuxKUFgNA3CLuUVIfXC3cc~h9YF00G8qKxvt~L0yJIgRe4YomYSnKCswcgTfVKN2guMp9kYldLlG4aPs5vxJFFi5N-P6EN7AItdTpaT-pPEnnackEIetoO4xDe4VoaYbMNO8P8iyW638Uw5lDwsZA__&Key-Pair-Id=K1C11UVRQNXLRQ"}
2025/10/15 12:35:00 AM XLIFF Server Communication No se pudo leer el archivo xliff. 187687 163003708 {"downloadUrl":"https:\/\/ate-production.s3proxy.wpml.org\/translated_xliffs\/xliffs\/115\/560\/385\/original\/translated_161731052_Confessions_of_an_Ex-Elder20251013-13701-remlep.xliff20251013-15923-2d5myr.xliff?Expires=1761093297&Signature=ZPq0yzDWfyCFWPa-xMTONHq7lpy5SqI0j8YHCdQY01fIkNEoMVkbIMEwR56OsjM7mEqkAT9vSgBE50lPrPNL5yh-e-f65AhfmIYS2UKSDdxT-0OBQCIXaXG9cbZ-WKzo-Rmtbe37iPPJo0kXQQhsJk3W1xWwrgmocHucCUTs1eHDsUxrXugP2EAenLMPWg21McIcIgrNr8YtpvJI3NNXTcS1Big~X5n3NO9vUYykAc1DfnE5CLQTzluA6soeMLhiDCVEcQzHJtuxRCmeBemHpRb64row~ecPvAnn4krYpLXOlljrymfpYjjDXvlORD8FK-4NRop2bQgQVZ4vAuXAyQ__&Key-Pair-Id=K1C11UVRQNXLRQ"}
2025/10/15 12:34:59 AM XLIFF Server Communication No se pudo leer el archivo xliff. 187688 163003787 {"downloadUrl":"https:\/\/ate-production.s3proxy.wpml.org\/translated_xliffs\/xliffs\/115\/560\/463\/original\/translated_161731132_when_it_comes20251013-7201-fvp78.xliff20251013-7201-14smxiy.xliff?Expires=1761093297&Signature=VMll4Wl8LnbQog6WCKckNsAeD6~i~2LGDIDVUtEU~Hn8EU1Rlzk0zmJgY0D9yG1nbMFJbezzWGFF05avPm2S43UiUa00UlTAmx4pjnT82JmMscnjrRz3MsK1ZVES1YiWQVQ-n2nBMwZfnLc5KTif8tgGIDhg9S~~QUKRMdoXhYLQQJqP12inzi14zEeqQnOZY03eSgxuTWgM5V8mRaFHXjDF1a6BG4okZzTINgQ3vdwO8bcAEO1uU9ijMu08OVZn8W1hmomoy9B0cmqC3rEfkKQEC7UtZZP000Gsm8fh4U6whQz-CBdzA0UQZkyq5Z6R3~vneu9NhIkUZFuLKhpOjQ__&Key-Pair-Id=K1C11UVRQNXLRQ"}
2025/10/14 9:22:55 PM XLIFF Server Communication The xliff file could not be read. 187767 163091892 {"downloadUrl":"https:\/\/ate-production.s3proxy.wpml.org\/translated_xliffs\/xliffs\/115\/622\/963\/original\/translated_161819146_when_it_comes20251013-3909-145gxby.xliff20251013-16543-1n62e7v.xliff?Expires=1761081772&Signature=Yj6oKVZz8tArucIzFJbugDQa98AYW4YCDtvf1TMwInyrzLfEp3oZ6hFuG4EphxjG6qZSR5d05XwQp8RqljgsfPcfjwYP9hg6~dlrEmDeRVTyMFV~CD-0OVLZHgD8clDEKdeRPmJX~APZbqnxX5MWqE4ZCOLha6ua94dK9kcW-7JQ3XOEumzllAtKeno8BYkvNIqcsXZmRqsbVtMIISKa5B8gYQaQSX9J0~WEHoQUNWK5lHIjZ~KeCMupX8EDoeaEQC4rSoutvn9wx662UiK9pmgFYQASvfgciaHm2oOR0AcVav85fX~fYy~vPW2HF29AWggV1fRfJH-0PuWTwvXAWg__&Key-Pair-Id=K1C11UVRQNXLRQ"}
The first entry is from the 14th:
2025/10/14 8:50:01 PM XLIFF Server Communication The xliff file could not be read. 187765 163091302 {"downloadUrl":"https:\/\/ate-production.s3proxy.wpml.org\/translated_xliffs\/xliffs\/115\/622\/743\/original\/translated_161818566_Confessions_of_an_Ex-Elder20251013-9804-1059w6k.xliff20251013-17022-1ftqz1e.xliff?Expires=1761079793&Signature=qscM5JET9y~0XzcB-WI8xQTqiok96KLzdJqParzTwwZkmWP2XP45IWefiZ3FtCbTDK1aoAPM9RXhP0OdCAf2xqA7P0diN6pT79Ul2FMHoSY6J8eckD7MRnMtDxJZ1szLUCzzqxFWBRQJFYDMIev5OpCOYv92kzQVXsUel1U3zx8uXZSzExXPxfvYyhyR3xe12unzLW6c-vBcCQ5nsojXD04TSRZpwqmhXLMeXaUmvq53riEvCBLREj9vCSWk5yCHRDfw1Q9Kog35YTYBjWjUsEMPPCdnzU0yzDwRu5bh2nyCASF3tqRXYjURqC43b-Sa~Vu1bIPftAzQPKGCdnmKdQ__&Key-Pair-Id=K1C11UVRQNXLRQ"}
These two posts "Confessions of an Ex-Elder" and "when it comes" have been problematic as the Spanish translation never seems to be able to finish for some reason.
I advised the client to re-write the English entries and try to re-translate them from scratch, but also that has not worked and these two are still "hanging".
> Regarding the load, with Auto Translate Everything enabled, you should be able to translate your entire website without any issues or performance problems.
If it were not my real experience your statement would almost be funny.
In my previous message I told you that automatic translation of the site simply did not work and I had to manually translate the 12,000 posts in batches of maximum 100.
I believe that with small(er) websites auto-translation is not a problem at all, but with this website, the ATE simply cannot handle the load. Telling me otherwise is not very helpful, nor constructive as it doesn't work towards a solution and instead tells me that I am wrong.
Thank you for sharing this with me. I completely understand your concerns, and I want to assure you that my response isn’t meant to downplay the issues you’re facing. Your case has been escalated to our ATE team, and I’ve been closely coordinating with them throughout this process to ensure it’s fully addressed.
After further discussions with the team, we’ve identified that this behavior is linked to a known issue affecting very large jobs. This is being resolved in the next major WPML release, which aligns with what you’re currently experiencing.
With the ATE error log you provided, the next step is for our ATE team to take a closer look at the backend. We won’t disable any plugins, our work will mainly involve sending and canceling jobs for testing purposes. Please rest assured that any credits used during this testing will be reimbursed immediately.
I am happy to hear that you changed your opinion on the matter 180 degrees and that the bug indeed is real for very large auto translation jobs.
We are currently in the process of changing hosting from WP Engine to Kinsta. I expect this is finished early next week, upon which time I will send you login details to the site.
Many thanks for your ongoing efforts to get this resolved.
Awesome, thank you for the updates and glad to hear the migration went well.
I would like to request temporary access (wp-admin and FTP) to your site to test the issue.
(preferably to a test site where the problem has been replicated if possible)
**Before we proceed It is necessary to take FULL BACKUP of your database and your website. Providing us with access, you agree that a backup has been taken **
I often use the Duplicator plugin for this purpose: http://wordpress.org/plugins/duplicator/
You will find the needed fields for this below the comment area when you log in to leave your next reply.
The information you enter is private which means only you and I have access to it.
NOTE: If access to the live site is not possible and the staging site does not exist please provide me with a duplicator package created with the duplicator plugin.
I'm afraid that you will have to do better than that.
We have no intention whatsoever to keep the superadmin access that we granted you for indefinite time, so you will have to give us a clear timeline for this.
Also you offered to reimburse credits to the client, something now seems "forgotten" since you don't mention anything about it.
Third, since you already acknowledged this is a bug, which will be solved in the next update, you will also need to give a timeline on that.
Please don't treat this like a feature request. WPML rolls out PTC with great fanfare, I recommend it to my client and now it turns out that PTC (and ATE) cannot handle very large, high traffic sites?!
Using your standard phrase of <italic>we will update you as soon as there are news.</italic> simply is not going to work and you need to do a LOT better!!!
Your ticket is still under review by the ATE team, this is not being treated with any less urgency and is an actively being debugged.
Regarding your credits -- I already provided extra credits in the beginning of our communication, as well as any credits used during our tests if any, will be reimbursed. This is not forgotten or dismissed.
Once I have any news you will be updated -- there is a team of developers working on this, when their debugging efforts are finished then we will update you.
