Issues with pages not being cached

I then toggled the plugin off and on and this appears to have fixed this.

I am little bit of confused and please clarify what do you mean by turn plugin off ? and fix what ?

In WordPress on the plugins page, there is the option to enable or disable any plugin.
This is not a new feature, it has always existed for as long as wordhas existed and supported plugins.

When something is broken, you need to make it not broken and make it work… this is called FIXING… so when something is no longer broken, you have FIXED it.

Not trying to be funny, but this is very very basic stuff, so if you don’t even understand how plugins work or what the word FIX means, you are obviously not going to be able to help.

yes, thanks for the class , I know what that is , I mean which plugin you disabled ?

what confuses me is that, if you are working on a cache-related-thing, and you disable the cache plugin ?

because if that so , whether it was working properly or not , it will stop working by then

Since this issue is related to LSCACHE and I am posting in the LSCACHE support forum, I am of course referring to the LSCACHE plugin.

okay please forgive my bluntness

you were having a frequent or unwanted purge that makes it cache: miss

and you disable LSCWP, then you don’t have frequent/unwanted purge ?

I just don’t understand this part , as you were trying to work on a cache/purge issue , why would you disable the cache plugin…

As stated, I noticed I was having issues with my sites using up loads of resources (this means memory and CPU.
I then noticed that most of the pages on the sites were showing a miss for the caching, and it seems they were either being missed or purging shortly after crawling each page.

I then toggled the LSCACHE plugin off and on (this means disabling the plugin and then re-enabling the plugin) and this appears to have fixed this.

But as stated, I manage over 20 websites, and don’t want to have to keep checking them all to make sure they are not having this issue, plus until I noticed this will be having a negative impact on speed and ranking. How can I avoid this issue occurring to begin with, what is the cause?

please check this page to grab some debug log and purge log , the log should tell something

it says

If the cause is not obvious, you’ll need to do a little digging. Enable the debug log, repeat the steps that cause a purge, disable logging, and then check the log to find the cause of any Purge All actions.

But there are no steps I can repeat to cause this.

please try raise the debug log size to higher , like 30M or 300M

then set debug log to “ON”

then wait for sometimes until that happens , then check on wp-content/debug.purge.log