Check WordPress Cron for Translation Jobs

TranslateSense relies on WordPress background scheduling to process bulk translation jobs for server-side providers such as OpenAI and Google Gemini. If jobs stay pending or progress stops, check the queue status and your site’s cron configuration before starting another batch. Chrome Built-in AI uses a browser-based workflow rather than the server-side cron queue.

Check the bulk queue first

1. Open the TranslateSense Translation Progress view and note whether the affected jobs are pending, running, completed, already existing, or failed.
2. Confirm that you selected a server-side provider. Chrome Built-in AI jobs do not run through the server-side cron queue.
3. Try a small test batch with a source post and target language you can safely review. Avoid repeatedly starting the same batch while earlier jobs may still be active.
4. If the progress view reports a failure, read the displayed error details. A provider/API or content error is not necessarily a cron problem.

Check WordPress cron and hosting

1. Ask your hosting provider or administrator whether WordPress cron requests and loopback/background requests are allowed on the site. Hosting security rules, firewalls, or disabled loopback requests can prevent scheduled work from running.
2. Check the site’s wp-config.php for the DISABLE_WP_CRON constant. If it is set to true, confirm that the site has an intentionally configured system cron or other supported scheduler. Do not change this setting blindly; coordinate with the site administrator or host.
3. If your site uses a hosting-level cron job, verify in the hosting control panel or server logs that it is enabled, runs at the intended interval, and completes without errors. The exact setup depends on the hosting environment.
4. If a cron inspection tool is already installed, look for the TranslateSense bulk hook translatesense_bulk_process_cron. The plugin registers it with a 60-second interval while bulk queue processing is needed. The plugin also attempts to spawn background cron processing after starting a batch and after processing a job.
5. Do not treat the separate translatesense_cache_cleanup event as proof that bulk translation is working. That is a different, daily cache-maintenance task.

Retest and continue troubleshooting

After your administrator or hosting provider confirms the scheduler is working, run a small bulk translation and watch the progress view. If jobs still remain pending, follow Why is a bulk translation still pending?. If jobs stop or fail, review Why did a bulk translation stop? and the available error details. Do not share API keys or other credentials in screenshots, logs, or support requests.

Screenshot to add: [WordPress cron inspection for the TranslateSense bulk queue]