Back to Community
Home / Community / Plugin → Litespeed cache

Troubleshooting LiteSpeed Cache Cron Job Issues: A Comprehensive Guide

33 threads Sep 7, 2025 Plugin → Litespeed cache

Content

Many WordPress site administrators using the LiteSpeed Cache plugin encounter issues with scheduled tasks, or cron jobs. These problems often manifest as warnings in the Site Health tool, missed notifications, or features like image optimization failing to run automatically. This guide will explain the common causes and provide practical solutions to get your scheduled tasks back on track.

Why Do Cron Job Issues Occur with LiteSpeed Cache?

The core of the problem lies in how WordPress handles scheduled tasks. WordPress uses a system called WP-Cron, which triggers scheduled events only when a page on your site is loaded. When LiteSpeed Cache is active and serving cached pages, these page visits may not always trigger the underlying PHP processes needed for WP-Cron to execute its tasks. This can cause events to be marked as "late" or prevent them from running altogether.

Common symptoms include:

  • Site Health warnings about a "late" event named litespeed_task_imgoptm_req or similar.
  • Image Optimization (auto-pull or auto-request) not processing automatically.
  • Critical CSS, Unique CSS, or LQIP (Low-Quality Image Placeholder) queues not clearing.
  • Notification emails or other plugin tasks failing to send.

Common Solutions for LiteSpeed Cache Cron Issues

1. Set Up a System Cron Job (Recommended)

The most effective long-term solution is to bypass the default WP-Cron system by defining a constant in your wp-config.php file and setting up a real system cron job.

  1. Edit your wp-config.php file: Add the following line above the /* That's all, stop editing! Happy publishing. */ comment. 
    define( 'DISABLE_WP_CRON', true );
    This tells WordPress to stop using its internal cron system.
  2. Create a system cron job: The method for this varies by hosting provider. In cPanel, you would navigate to the Cron Jobs section. The command to run typically looks like this, replacing example.com with your domain: 
    wget -q -O - https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1
    A common and effective interval for this cron job is every 5 minutes (*/5 * * * *). This is often sufficient and less resource-intensive than the default 1-minute interval used by some LiteSpeed tasks.

This approach ensures that wp-cron.php is triggered directly and regularly by the server itself, independent of visitor traffic.

2. Verify Image Optimization Settings

If you are not using the Image Optimization feature but are still seeing frequent admin-ajax.php requests for imgoptm, the feature may not be fully disabled.

  1. Navigate to LiteSpeed Cache > Image Optimization in your WordPress admin dashboard.
  2. Ensure all optimization settings are turned Off.
  3. Scroll down and click the Destroy All Optimization Data button. This is a crucial step to fully deactivate the background processes.

3. Check for IP Address Conflicts (Quic.cloud Users)

If Image Optimization requests are sent to Quic.cloud but are never pulled back, an IP misconfiguration might be the cause. This can happen if you use a service like Cloudflare, which masks your server's origin IP.

  1. Log in to your Quic.cloud dashboard.
  2. Ensure your domain is linked.
  3. Navigate to your domain's settings and verify that the Server IP field contains your origin server's correct IP address, not the IP of a proxy or CDN service.
  4. Return to your WordPress admin, go to LiteSpeed Cache > Image Optimization, and click Clean Up Unfinished Data before sending a new optimization request.

4. Investigate with a Report Number

For more complex issues, generating a report from within the plugin can provide vital clues.

  1. Go to LiteSpeed Cache > Toolbox > Report.
  2. Click Send to LiteSpeed to generate a unique report ID.
  3. This ID can be used to seek help in community forums, allowing others to review your configuration.

Conclusion

Cron-related issues with LiteSpeed Cache are almost always a configuration challenge rather than a permanent bug. The most reliable fix is implementing a system cron job to reliably trigger WP-Cron. For issues specific to Image Optimization, ensuring the feature is fully disabled or that your server IP is correctly configured in Quic.cloud often resolves the problem. The LiteSpeed Cache team is consistently working on improvements, as seen in recent updates aimed at reducing unnecessary cron activity.

Related Support Threads Support