Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter vineesh1994

    (@vineesh1994)

    Hi There,

    We reviewed the Scheduled Actions logs during both normal traffic and high-concurrency checkout scenarios and wanted to share our findings.

    During normal traffic (no active orders), we only see expected low-frequency maintenance actions such as WPForms tasks, WP Mail SMTP notifications, and WooCommerce cleanup jobs. These actions are scheduled and not triggered by checkout activity.

    However, during concurrent checkouts, we consistently see a spike in WooCommerce-generated background tasks, specifically:

    • wc-admin_import_orders (WooCommerce Admin / Analytics)
    • wc_delete_related_product_transients_async (WooCommerce core cache cleanup)

    These actions are created once per order and, under high concurrency, are scheduled multiple times within the same second. This causes a noticeable increase in the Action Scheduler queue size and correlates directly with slower order processing.

    At this point, we do not see evidence of third-party plugins adding checkout-time scheduled actions. The queue pressure appears to be coming from WooCommerce core and WooCommerce Admin tasks triggered during order creation.

    Based on this, we believe the performance impact is related to how these WooCommerce background jobs scale under concurrent checkout load, rather than a plugin conflict.

    Please let us know if you’d recommend:

    • Disabling or deferring WooCommerce Admin analytics imports, or
    • Any best practices for handling these background tasks under high concurrency.

    Thanks for your guidance.

    These are the logs :

    wc_delete_related_product_transients_async Run | Cancel Pending ‘post_id’ => 1016961 wc_delete_related_product_transients_group Non-repeating 2026-01-26 12:27:08 +0000 (Now!) 2026-01-26 12:27:08 +0000 action created

    wc_delete_related_product_transients_async Run | Cancel Pending ‘post_id’ => 1016961 wc_delete_related_product_transients_group Non-repeating 2026-01-26 12:27:08 +0000 (Now!) 2026-01-26 12:27:08 +0000 action created

    wpforms_process_forms_locator_scan Run | Cancel Pending ‘tasks_meta_id’ => 1 wpforms Every 1 day 2026-01-27 04:18:29 +0000 (15 hours 51 minutes) 2026-01-26 04:18:29 +0000 action created woocommerce_cleanup_draft_orders Run | Cancel Pending Every 1 day 2026-01-27 04:18:29 +0000 (15 hours 51 minutes) 2026-01-26 04:18:29 +0000 action created wp_mail_smtp_admin_notifications_update Run | Cancel Pending 0 => 256 wp_mail_smtp Every 1 day 2026-01-27 04:18:29 +0000 (15 hours 51 minutes) 2026-01-26 04:18:29 +0000 action created wpforms_process_purge_spam Run | Cancel Pending ‘tasks_meta_id’ => 2209 wpforms Every 1 day 2026-01-27 04:18:29 +0000 (15 hours 51 minutes) 2026-01-26 04:18:29 +0000 action created

    wpforms_email_summaries_fetch_info_blocks Run | Cancel wc-admin_import_orders Run | Cancel Pending 0 => 1017171 wc-admin-data Non-repeating 2026-01-26 12:27:07 +0000 (39 seconds ago) 2026-01-26 12:27:02 +0000 action created wc-admin_import_orders Run | Cancel Pending 0 => 1017172 wc-admin-data Non-repeating 2026-01-26 12:27:07 +0000 (39 seconds ago) 2026-01-26 12:27:02 +0000 action created

    wc-admin_import_orders Run | Cancel Pending 0 => 1017173 wc-admin-data Non-repeating 2026-01-26 12:27:07 +0000 (39 seconds ago) 2026-01-26 12:27:02 +0000 action created wc-admin_import_orders Run | Cancel Pending 0 => 1017174 wc-admin-data Non-repeating 2026-01-26 12:27:07 +0000 (39 seconds ago) 2026-01-26 12:27:02 +0000 action created

    Thread Starter vineesh1994

    (@vineesh1994)

    We are currently performing all testing on our staging environment. At this stage, we have not deactivated plugins, as the active plugins are essential to the checkout and order processing flow even on staging. However, we did test concurrent checkout requests with the existing setup.

    During testing, orders are successfully created and processed, but under concurrent load the processing time increases noticeably.

    We also reviewed WooCommerce → Status → Scheduled Actions for the latest concurrent orders. The primary actions created at checkout time are:

    • wc-admin_import_orders (non-repeating, created per order)
    • woocommerce_deliver_webhook_async (multiple webhooks per order)

    These actions are being queued as Pending and are not failing, which indicates that Action Scheduler is functioning as expected. The slowdown observed under concurrency appears to be related to queue pressure and available server resources rather than order creation failures.

    We understand the importance of isolating third-party impact and will proceed with a plugin/theme conflict test on the staging environment (WooCommerce only + Storefront) to confirm whether the behavior persists without third-party plugins.

    Please let us know if there is any additional data you would like us to collect during the staging test.

    These are the logs of WooCommerce → Status → Scheduled Actions:

    wc-admin_import_orders
    Run | Cancel
    Pending
    0 => 1017023
    wc-admin-data Non-repeating 2026-01-23 11:53:13 +0000
    (14 seconds ago)
    2026-01-23 11:53:08 +0000
    action created

    wc-admin_import_orders
    Run | Cancel
    Pending
    0 => 1017024
    wc-admin-data Non-repeating 2026-01-23 11:53:13 +0000
    (14 seconds ago)
    2026-01-23 11:53:08 +0000
    action created

    wc-admin_import_orders
    Run | Cancel
    Pending
    0 => 1017025
    wc-admin-data Non-repeating 2026-01-23 11:53:17 +0000
    (10 seconds ago)
    2026-01-23 11:53:12 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 12
    'arg' => 1017023
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:18 +0000
    (9 seconds ago)
    2026-01-23 11:53:18 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 13
    'arg' => 1017023
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:18 +0000
    (9 seconds ago)
    2026-01-23 11:53:18 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 12
    'arg' => 1017022
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:18 +0000
    (9 seconds ago)
    2026-01-23 11:53:18 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 13
    'arg' => 1017022
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:18 +0000
    (9 seconds ago)
    2026-01-23 11:53:18 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 12
    'arg' => 1017024
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:18 +0000
    (9 seconds ago)
    2026-01-23 11:53:18 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 13
    'arg' => 1017024
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:18 +0000
    (9 seconds ago)
    2026-01-23 11:53:18 +0000
    action created

    woocommerce_deliver_webhook_async
    Run | Cancel
    Pending
    'webhook_id' => 12
    'arg' => 1017025
    woocommerce-webhooks Non-repeating 2026-01-23 11:53:22 +0000
    (5 seconds ago)
    2026-01-23 11:53:22 +0000
    action created
    • This reply was modified 4 months, 3 weeks ago by vineesh1994.
    Thread Starter vineesh1994

    (@vineesh1994)

    Our WooCommerce site is hosted on Cloudways. I’ve initially contacted the Cloudways support team regarding the performance concerns, and they reviewed the server configuration. As part of that process, they increased the PHP workers and confirmed that CPU, memory, and process limits are already set to their recommended maximums for our server.

    Cloudways advised that the server-side configuration does not appear to be the bottleneck and suggested reaching out to the plugin/application support team for further investigation.

    I’m now begun testing the recommended steps on a staging environment and will continue with the remaining checks. We’ll update you with our findings once testing is complete.

    Thanks for your support.

    Thread Starter vineesh1994

    (@vineesh1994)

    Thank you for your guidance.

    We’ve now completed the requested steps on a staging environment:

    WordPress and WooCommerce have both been updated to their latest versions.

    The active theme was reviewed; there are no newer theme updates currently available.

    The theme does include a number of overridden WooCommerce templates which are flagged as outdated after the WooCommerce update.

    After completing the updates, we carried out functional testing across key flows, including product pages, cart, checkout, order placement, and order management in the admin area so the functionality is working. But, we did not any changes, the performance and everything still the same and the problem is not solved yet.

    Given that the site is functioning correctly, we have not yet updated the overridden WooCommerce templates, as these are legacy customizations and updating them wholesale could introduce regressions. At this stage, the outdated template notices do not appear to be contributing to the reported issue.

    Please let us know if you’d recommend proceeding with a plugin/theme conflict test despite the absence of issues, or if there are specific templates or logs you’d like us to review next.

    Thanks again for your assistance.

    System Report Github Link : https://gist.github.com/vineeshw1994/58c19b2763ce1decc5e3be1da1bdef59

    Thread Starter vineesh1994

    (@vineesh1994)

    Thread Starter vineesh1994

    (@vineesh1994)

    I have shared the system report link in your slack account. please check it out.

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