Back to Community
Home / Community / Plugin → Litespeed cache

Troubleshooting Unexpected 'Purged All Caches Successfully' Messages in LiteSpeed Cache

22 threads Sep 7, 2025 Plugin → Litespeed cache

Content

Why Am I Seeing Constant 'Purged All Caches Successfully' Messages?

Many WordPress site administrators using LiteSpeed Cache encounter a confusing issue where the "Purged all caches successfully" notification appears repeatedly in their dashboard, often after every page refresh or administrative action. This behavior is not only annoying but can indicate an underlying configuration problem that might be affecting your site's performance.

Common Causes of Automatic Cache Purges

Based on community reports and troubleshooting threads, several factors can trigger this behavior:

  • Object Cache Configuration: Enabling Object Cache (particularly with memcached) has been frequently associated with this issue. The constant purge messages appear only after Object Cache is activated.
  • Plugin or Theme Conflicts: Custom code in your theme or plugins might be triggering the purge_all action unintentionally. Some hosting provider plugins have also been identified as potential culprits.
  • Scheduled Tasks: Cron jobs or scheduled maintenance tasks that include the do_action('litespeed_purge_all') function can cause systematic purging.
  • Admin Session Timeouts: Some users report that logging into wp-admin after several hours of inactivity automatically triggers a full cache purge.

Step-by-Step Troubleshooting Guide

1. Enable Debug Logging

The first step in diagnosing this issue is to enable detailed logging:

  1. Navigate to LiteSpeed Cache → Toolbox → Debug Log
  2. Set Debug Log to "ON"
  3. Set Debug Level to "Advanced"
  4. Set an appropriate log size (e.g., 30MB)
  5. Visit a few admin pages to generate log data
  6. Check Toolbox → Log View for purge-related entries

2. Check for Plugin Conflicts

Temporarily disable plugins, particularly those provided by your hosting company, to see if the purge messages stop appearing. Hostinger-specific plugins have been mentioned in several reports as potential causes.

3. Verify Object Cache Settings

If you recently enabled Object Cache, try disabling it temporarily to see if the purge behavior stops. The connection between Object Cache activation and automatic purging is well-documented in user reports.

4. Review Custom Code

Examine your theme's functions.php file and any custom plugins for code that might be triggering purge actions. Look for instances of:

do_action('litespeed_purge_all')

or similar purge-related functions that might be executing unnecessarily.

5. Generate a Report Number

For more advanced troubleshooting, generate a diagnostic report:

  1. Go to LSC → Toolbox → Reports
  2. Click "Send to LiteSpeed"
  3. Share the generated report number with support communities

Advanced Investigation

If the basic troubleshooting steps don't resolve the issue, consider these advanced techniques:

Monitor Hook Execution: The litespeed_purged_all action hook fires after a successful purge operation. You can hook into this action to track when purges are occurring:

add_action('litespeed_purged_all', 'track_purge_events');
function track_purge_events() {
    error_log('Cache purge occurred at: ' . date('Y-m-d H:i:s'));
}

Check Scheduled Tasks: Review your WordPress cron jobs to see if any scheduled tasks include cache purging functionality that might be running too frequently.

When to Seek Additional Help

If you've tried all these steps and continue to experience unexpected purge messages, consider:

  • Checking with your hosting provider to ensure their server configuration isn't triggering purges
  • Consulting the official LiteSpeed Cache documentation for additional debugging techniques
  • Searching through community forums for similar reports and solutions

Remember that persistent automatic purging can significantly impact site performance by constantly invalidating cached content, so resolving this issue should be a priority for maintaining optimal site speed.

Related Support Threads Support