Operation timed out error
If the AI provider's API takes too long to respond, the request will be aborted by the plugin's HTTP client and the translation will fail with an error along these lines:
2026-05-20T03:11:48+00:00 Error [Query "translate-customposts"] Execution with errors: 🔴 Translation to es_AR failed - The API for provider 'ChatGPT' returned error: cURL error 28: Operation timed out after 60000 milliseconds with 0 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://api.openai.com/v1/chat/completionsThe key part is cURL error 28: Operation timed out after N milliseconds. It means the request reached the Translation Timeout limit configured in the plugin before the API finished responding.
Raise the Translation Timeout
Go to the Settings page, under Plugin Configuration > Translation Timeout, and increase the value.
Keep the value below your server's max_execution_time (set in php.ini, or via your hosting control panel) so a stalled translation still fails cleanly with a controlled error in the logs — instead of triggering the generic server timeout (HTTP 502 / 504, or a blank "Maximum execution time of N seconds exceeded" page).
If your translations regularly time out, raise both the Translation Timeout and your server's max_execution_time in tandem.
Reduce the payload sent in each request
A complementary fix is to send shorter requests, so each one resolves faster and is less likely to hit the timeout.
Go to Settings > Service Configuration > [AI service], and decrease the Max request payload length option to an adequate number of characters.
For instance, if it is set to 4000 and it still fails, try 2000.
When the payload is reduced, the translation is split into multiple smaller requests, each of which is resolved faster.
See also Avoiding timeouts in the PHP server.