Action Triggering Cache Purges

  • Resolved john.p

    (@peppas)


    1 year, 1 month ago

    On litespeed I find logs like these:

    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] 💓 ——POST HTTP/1.1 (HTTPS) /wp-admin/admin-ajax.php
    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] Query String: action=as_async_request_queue_runner&nonce=ca82652777
    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] User Agent: WordPress/6.8.1; https://pharmacy2you.gr
    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] Accept: */*
    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] Accept Encoding: br,gzip
    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] X-LSCACHE: true
    05/08/25 19:53:51.675 [65.109.239.143:43208 1 MjA] X-LiteSpeed-Purge: public,327_Po.14088,327_URL.6666cd76f96956469e7be39d750cc7d9,327_W.recent-posts-5,327_FD,327_REST => LiteSpeed\LSC->send_headers()@603 => WP_Hook->apply_filters(,ARRAY)@324 => WP_Hook->do_action(ARRAY)@348 =>
    /home/runcloud/webapps/pharmacy2you/wp-includes/load.php@517

    I am led to believe this is related to actions from your plugin, specifically:

    adt_pfp_as_generate_product_feed_batchComplete

    • 'feed_id' => 14088
    • 'offset' => 0
    • 'batch_size' => 750

    adt_pfp_as_generate_product_feed_batch_14088Non-repeating2025-05-09 08:02:16 +0000
    (1 hour 52 minutes ago)

    1. 2025-05-09 08:02:15 +0000
      action created
    2. 2025-05-09 08:02:22 +0000
      action started via Async Request
    3. 2025-05-09 08:02:43 +0000
      action complete via Async Request

      What is this action and why does it trigger a cache purge every single hour?
Viewing 4 replies - 1 through 4 (of 4 total)
  • Tanvir Hasan

    (@tanvirh)

    1 year, 1 month ago

    Hi @peppas

    Thank you for sharing the log entries.

    The action adt_pfp_as_generate_product_feed_batch_14088 is a scheduled asynchronous task triggered by the Product Feed PRO plugin to generate or update product feeds in batches. The parameters like 'offset' => 0 and 'batch_size' => 750 indicate that the process is running in chunks to prevent timeouts or memory issues.

    The recurring nature of this action, approximately every hour, suggests it’s being scheduled through WP-Cron or the Action Scheduler, both of which the plugin uses for background processing. During feed generation, the plugin updates custom post types and product metadata, often via functions like wp_insert_post and update_post_meta. These updates can invoke WordPress hooks such as save_post or update_option, which LiteSpeed monitors and responds to by purging relevant cached content.

    By default, Product Feed PRO may be set to regenerate feeds on an hourly basis. To adjust this behavior, navigate to Product Feed PRO → Manage Feeds and review the scheduling options. If you don’t require hourly updates, consider changing the frequency to daily or twice daily to reduce cache purging.

    Hope this explanation and guidance help clarify the behavior you are seeing.

    Cheers!

    Thread Starter john.p

    (@peppas)

    1 year, 1 month ago

    1st of all, my main problem is I can’t find which feed it is. You are not using post id in your feeds url, which is the one referenced in the logs.
    2nd, why is this expected behaviour? Why would a feed need to update post meta and therefore trigger a cache clear? Am I the only one that has an issue with the cache being cleared as soon as your plugin runs?

    Thread Starter john.p

    (@peppas)

    1 year, 1 month ago

    1st of all, i can’t find which feed it is. Your feeds dont use post ids, which is referenced in the wp and litespeed logs.

    2nd, why is this expected behaviour? Why would you need to update metadata and save posts to generate the feed, and thus trigger cache clears?

    Am I the only one that has an issue with the cache being cleared that frequently due to actions on your plugin?

    Tanvir Hasan

    (@tanvirh)

    1 year, 1 month ago

    Hi @peppas

    You are correct, feeds do not currently use post IDs, which makes it difficult to trace logs. We have noted this as a feature request for future improvement.

    The plugin updates product metadata during feed generation to ensure accuracy, which may trigger cache clearing, especially with LiteSpeed.

    You are not the only one experiencing this. Our team is reviewing ways to minimize unnecessary cache purges in future updates.

    We appreciate your feedback and patience.

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Action Triggering Cache Purges’ is closed to new replies.