TranslateSense processes bulk translations through a queue for server-side providers such as OpenAI and Google Gemini. The plugin schedules background work, processes queued jobs, and reports each job’s result in the bulk translation progress view. Chrome Built-in AI uses a separate browser-based workflow and is not processed by the server-side cron queue.
Choose the right guide
- Understand Background Translation Processing to learn how server-side jobs move through the queue.
- Check WordPress Cron for Translation Jobs when queued jobs do not appear to progress.
- Monitor Bulk Translation Progress to review job statuses and results.
- If a job stays pending, follow Why is a bulk translation still pending?. If processing stops or fails, see Why did a bulk translation stop?.
How scheduled processing works
For server-side providers, TranslateSense creates a job for each source post and target language. The queue worker selects pending jobs in order and processes them one at a time. The plugin registers a recurring WordPress cron hook for the bulk queue and also attempts to trigger background processing after a batch starts or a job finishes. WordPress cron still depends on the site’s WordPress and hosting environment.
TranslateSense also has a separate daily cache-cleanup task. That task is not the bulk translation worker, so a cache-cleanup event alone does not prove that queued translations are running.
Screenshot to add: [TranslateSense bulk translation progress overview]