Dashboard Last Requested timestamps

  • Resolved Mijnheer Eetpraat

    (@eetpraat)


    2 weeks ago

    I’ve got some questions/remarks on the Dashboard of the LiteSpeed Cache WordPress plugin v6.5.2

    1. QUIC.cloud Service Usage Statistics does not seem to refresh automatically. When I ran out of my Remaining Daily Quota for Image Optimization yesterday, it did not refresh and restart Image Optimization today. I had to manually click Sync to restart Image Optimization. Is this expected or should this work automatically?

    2. CRON is running fine and all Litespeed tasks run every minute with status “Completed”, according to “WP-Cron Status Checker” (image 1). However, the LiteSpeed Cache Dashboard (image 2) does not seem to reflect that.

    Critical CSS has a queue, but a Last Requested timestamp of hours ago.

    Unique CSS has a queue, but a Last Requested timestamp of yesterday.

    Low Quality Image Placeholder has a queue, but a Last Requested timestamp of 43 minutes ago.

    Viewport Image (VPI) has a queue, but shows no timestamp at all.

    Question: shouldn’t these Last Requested timestamps be all the same, and one minute ago?

    3. If I use Force Cron on these four items, the queue seems to disappear but the Last Requested timestamp does not update. Is this expected or should this update automatically?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support litetim

    (@litetim)

    @eetpraat
    Can you share me the report number from LSC=>Toolbox=>Report
    We can look into some settings there and give you a more accurate respond.

    Thread Starter Mijnheer Eetpraat

    (@eetpraat)

    Report number:?TVVOTHOC
    Report date:?11/08/2024 12:35:20

    Plugin Support qtwrk

    (@qtwrk)

    1. the usage stats is sync’ed every 24 hours , ref: https://github.com/litespeedtech/lscache_wp/blob/7c707469b3c88b4f45d9955593b92f9aeaed54c3/src/cloud.cls.php#L260
    2. the cron status only report the cron job has been executed , it doesn’t necessarily mean the generation is completed , the generation is an asynchronous process by queue , the plugin will send or push the queue to generator server, this is 2 ways communication , which means the generator server will also decide to accept or not based various factors (your quota , your pending queue , processing queue …etc ) , for example if the queue is also pushed to generator and pending for process, then no matter how many times you cron it , it won’t change anything.
    3. this could mean the queue newly pushed is the duplication of pending queue , so it’s de-duplicated.

    to verify if UCSS/CCSS/LQIP/VPI works correctly or not , you can go to toolbox -> debug setting -> set debug log to ON , debug level to advanced , add notify_ into debug include URI

    then wait for a day or two (due to daily limit) , and check the debug log , if you see bunch of request showing like notify_ccss or notify_ucss , or notify_vpi or notify_img …etc , anything start with ?rest_route=/litespeed/v1/notify_xxxx , it means the generator server is sending the generated result back to your site.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.