I am writing to report a persistent and frustrating issue I am experiencing with the **Preload** feature in the WP Super Cache plugin.
The problem is that the **cache generation process does not complete successfully**. The preload function starts running, but the **cache that has been generated is consistently deleted or cleared before the preloading process can finish**.
I have thoroughly investigated this issue and attempted multiple troubleshooting steps, including:
* Checking and increasing my server's PHP memory limit.
* Disabling other plugins to check for conflicts.
* Adjusting the preload settings (e.g., reducing the number of posts/pages to preload).
* Manually clearing the existing cache before starting the preload.
Despite all these efforts, the issue remains. The cache is continuously cleared mid-process, resulting in an incomplete and ineffective preloaded cache.
I kindly request your assistance in diagnosing and resolving this problem. Any guidance or specific instructions would be greatly appreciated.
The issue is possibly caused by a conflict with the plugin’s Garbage Collection settings, which we recommend should be disabled if you enable Preload mode.
Could you please go to Settings > WP Super Cache > Advanced, scroll to the “Expiry Time & Garbage Collection” section, and check that Cache Timeout is set to 0, or at least something long (like 86400 seconds).
After adjusting those, try running the preload again.
I followed all the steps you mentioned, but the issue is still not resolved. I disabled the Garbage Collection settings as recommended and set the Cache Timeout to 0 (and also tested with a long value like 86400).
However, the problem continues: the Preload process stops after less than 30 minutes and then starts again from the beginning, so it never completes.
To avoid any cache refresh conflicts, I also disabled all options that could trigger automatic cache clearing and kept only manual cache mode enabled.
I also tested the plugin in both Simple Mode and Expert Mode, but the issue still occurs in both cases.
Please advise on what further steps I can take to fix this issue.
We’d like to take a closer look at your current settings to better understand what might be triggering the resets.
Could you please share uncropped screenshots of your Advanced and Preload tabs under Settings > WP Super Cache? This will help us identify any possible issues with the relevant configurations.
I’ve now attached the current WP Super Cache settings from both the Advanced and Preload tabs exactly as they are on my site.
Could you please review them and let me know whether these settings are suitable for enabling Preload properly? And if not, what changes or additional options do you recommend so that Preload can complete without restarting?
Just to confirm: I have already disabled the “Refresh preloaded cache files every X minutes” option, so it is set to 0, yet the Preload process still stops and restarts before finishing.
I appreciate your guidance and look forward to your advice.
At this stage, we’d recommend testing with a clean slate to rule out any plugin conflicts or lingering config issues that might be interfering with the Preload process. Here’s what we suggest:
Temporarily deactivate other caching or performance-related plugins (e.g., WP Rocket, W3 Total Cache, Autoptimize, LiteSpeed Cache, etc.)
Reset WP Super Cache settings to default, then re-enable the Preload mode keeping Garbage Collection disabled and the preload refresh time set to 0.
Monitor your server resource usage (CPU/memory/disk I/O) during the preload process to rule out hosting-level constraints. Your host can help you with this step and confirm if you’re hitting any limits.
If the issue continues even after these tests and is not related to hosting limits, please enable debugging under Settings > WP Super Cache > Debug, and once done, please try running the preload again and share the resulting debug logs with us.
Do you have updates about the above? We usually close inactive threads after one week of no activity, but we want to make sure we’re all set before marking it as solved. Thanks!