For server-side providers, TranslateSense creates a queued job for each source post and target language. The background worker processes these jobs without requiring you to translate every post manually from the editor, while the progress view reports the result of each job.
What happens to a queued job
- When a bulk batch starts, TranslateSense creates a job for each selected post and target language. If a translation already exists, the job can be marked Already Exists instead of being queued for translation.
- For server-side providers, TranslateSense schedules the bulk queue worker and attempts to trigger background processing.
- The worker selects the next pending server-side job, marks it as running, and extracts the source strings from the post’s translation packages or content.
- TranslateSense sends the extracted strings to the selected provider, maps the returned translations to the source content, and runs the post-translation step.
- The job is marked Completed when the translation step succeeds, or Failed if processing throws an error. Review the progress view and inspect the resulting post before relying on the translation.
- If more server-side jobs remain, TranslateSense attempts to trigger another worker tick. When no pending or running server-side jobs remain, it clears the bulk queue’s scheduled event.
Understand job statuses
- Pending / Queued: The job is waiting for a worker to process it.
- Running: The worker is processing the job. If a server-side job remains in this state for more than 10 minutes without an update, the worker can reset it to pending and set its progress message to “Restarting after timeout”.
- Completed: The job’s translation step finished successfully. Review the target post and its language relationship.
- Already Exists: TranslateSense detected an existing translation for the source post and target language.
- Failed: An error occurred during processing. Review the error details and fix the underlying issue before retrying.
Server queue versus browser-based translation
Chrome Built-in AI uses a browser-based workflow and is excluded from the server-side cron queue. If you use that provider, keep the supported browser and language requirements in mind and follow the browser’s progress interface. For server-side jobs that remain queued, use Check WordPress Cron for Translation Jobs. For stalled or failed batches, see Monitor Bulk Translation Progress, Why is a bulk translation still pending?, and Why did a bulk translation stop?.
Screenshot to add: [TranslateSense server-side job status and progress details]