qtwrk

yeah… sounds like something that will trigger purge all

I can help you to suppress the purge initiated by it , but I am not sure if it is a good idea

please provide the report number

you can get it in toolbox -> report -> click “send to LiteSpeed”

thanks for the suggestion , we are also refactor the crawler feature in upcoming version , as well as we need re-work on the document , I must say , even to me , if I didn’t dig the code directly , it was somewhat confusing as well

try put these files mentioned by woodmart support, into BOTH JS exclude and JS defer exclude , purge all , see how it happens

if you can also ask them , if there is any inline JS involved, you may need to exclude inline JS as well.

all good now ?

the checker doesn’t exactly work like a real browser

you can try re-open that page again on private window, and see if it gives you cache on 2nd or later access

yeah … it looks like you have quite some 3rd party javascript that slowing thing down , not sure what we can do about it

go to debug setting , set debug to ON , debug level to advance , debug include URI, add litespeed_type= into that field , save

then go to log view section ,clean up any existing log

then wait for 5 minutes , manual start it , if nothing happens , wait for another 5 minutes , manual start it again , then go to log view , share me the debug log it generates

try set interval to , at least 61 , or better 300 seconds or more

did manual start work ?

no , it’s not our doing

please try the steps this page provides

please provide the report number

you can get it in toolbox -> report -> click “send to LiteSpeed”

could you please do me a full-screenshot of the error ?

please provide the report number

you can get it in toolbox -> report -> click “send to LiteSpeed”

by any change, does your site have multiple-domains ? or it was copied/cloned from a stage/dev site or similar ?