Skip to content

Translation stuck in “Queued” or “Translating…” status

On this page

Applies to AI translation with the PRO add-on. LATW Cloud translates on its own servers, does
not use WP-Cron and is not affected.

AI translations started in wp-admin are not done while you wait: they go into a queue, and the queue
is worked through in the background by WordPress’s scheduler, WP-Cron, once a minute – a few
translations per run. Until a translation’s turn comes, it shows as Queued, and while it is with
the AI provider, as Translating….

If translations stay in that state, first check the Processing Mode in LATW Multilingual →
Settings → AI
. In Batch mode a delay is normal: the provider returns most batches within an
hour, Anthropic often only after several hours, and up to 24 hours at busy times (see
Translation Engine – AI Providers). In Synchronous mode a translation should appear within a
minute or two, and in Background mode (OpenAI) within a few minutes; if it does not, WP-Cron is
not running.

#Why WP-Cron stops

WP-Cron is not a real timer. It runs only when somebody opens a page of the site and that visit
reaches WordPress. So the queue stands still when:

  • the site gets few visits – a staging site, or a new site nobody visits yet;
  • a page-caching plugin (LiteSpeed Cache, WP Rocket and others) or a CDN answers most visits from
    its cache, so WordPress itself hardly runs – the queue then moves slowly or in bursts even on a
    busy site;
  • define( 'DISABLE_WP_CRON', true ); is set in wp-config.php and nothing on the server replaces
    it.

When WP-Cron has not run on time, Tools → Site Health usually shows “A scheduled event is late”
or “A scheduled event has failed” – a sign that the queue is affected too.

A cron job on the server runs the queue every minute whether or not anyone visits the site. This is
the reliable setup, and the one to use before translating a whole site into a new language.

  1. Add this line to wp-config.php, above /* That's all, stop editing! */:

    define( 'DISABLE_WP_CRON', true );
  2. Add a cron job that runs every minute, in your hosting panel or the server’s crontab. With
    WP-CLI:

    * * * * * wp cron event run --due-now --path=/path/to/your/wordpress

    or, without WP-CLI, by calling your site’s wp-cron.php (use your own address):

    * * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron > /dev/null

If you cannot set up cron jobs yourself, ask your hosting provider to do it – it is a common request.
Do step 1 only together with step 2: with WP-Cron disabled and no server cron job, the queue stops
completely.

#Fix: process the queue by hand

  1. In LATW Multilingual → Settings → Advanced, turn on Manual Check Responses and save.
  2. A Check Responses button appears next to the heading of the Posts, Taxonomies,
    Strings, Themes & Plugins and History screens.
  3. Each click sends up to 10 queued translations to the AI provider and collects the ones that are
    ready.

This does not replace WP-Cron: the queue moves only while you keep clicking. Use it to finish a few
translations now, or to check whether the queue works at all; for anything larger, set up the server
cron job above.