• Resolved tomenr

    (@tomenr)


    Unfortunately, I am having a problem with Scheduled Actions. Action Scheduler: 23 past-due actions found; something may be wrong. Apparently something is not working and I can no longer see the updated statistics.

Viewing 6 replies - 16 through 21 (of 21 total)
  • Plugin Support Ejay F – a11n

    (@ejayfernandes)

    Hi there,

    Since there’s been no recent activity on this thread, I’m marking it as resolved. Don’t hesitate to start a new thread if you need help in the future.

    If you have a few minutes, we’d love if you could leave us a review: https://ww.wp.xz.cn/support/plugin/woocommerce/reviews/

    Thread Starter tomenr

    (@tomenr)

    Hi, sorry for my delayed response.
    I run the conflict test on a staging website, but nothing new has happened.
    I stille have more then 1000 past-due-actions
    https://image2url.com/r2/default/images/1773929805976-8472b0b1-4d47-48f1-b17c-86812e641238.png

    Thread Starter tomenr

    (@tomenr)

    I see a lot of these hooks:

    woocommerce_run_update_callback

    • 'update_callback' => 'wc_update_1060_add_woo_idx_comment_approved_type_index'

    Plugin Support LovingBro (woo-hc)

    (@lovingbro)

    Hi @tomenr,

    From what you have shared and the screenshot, the issue appears to be tied to stalled Action Scheduler tasks, particularly those related to database updates like woocommerce_run_update_callback. When these pile up, imports and analytics processing can get stuck.

    Here are a few steps that should help move things forward:

    1. Run pending scheduled actions manually
      Go to WooCommerce > Status > Scheduled Actions, filter by “Pending” and “Past-due”, then try running a few actions manually to see if they complete or fail.
    2. Check for fatal errors
      Navigate to WooCommerce > Status > Logs and look for recent fatal errors, especially related to database updates or Action Scheduler.
    3. Increase server resources temporarily
      Imports and database updates can be resource intensive. If possible, increase:
      • PHP memory limit to at least 256M
      • Max execution time
      • Ensure WP-Cron is running properly
    4. Run WP-Cron manually
      If WP-Cron is not firing reliably, you can trigger it manually by visiting:
      https://your-site.com/wp-cron.php?doing_wp_cron
    5. Retry the import
      After clearing or processing some actions, try clicking Re-import Data again.
    6. Check for plugin or theme conflicts
      Since you mentioned testing on staging, kindly confirm if the issue persists with only WooCommerce active and a default theme like Storefront.

    To take a closer look, could you share your full System Status Report via:
    WooCommerce > Status > Get system report, then paste it to https://pastebin.com or https://gist.github.com and share the link here

    Also, if you notice any specific errors when running scheduled actions manually, a screenshot via https://snipboard.io would be very helpful.

    Looking forward to your update so we can narrow this down further.

    Thread Starter tomenr

    (@tomenr)

    I was checking your list and in “Site Health Status” I got this recommended improvement:

    Your PHP opcode cache’s interned strings cache needs more RAM allocated to it.Performance

    500 megabytes are allocated to PHP’s opcode cache. It is 50% full. Learn how to configure it.(opens in a new tab)
    8 megabytes are allocated to the opcode cache’s strings buffer. It is full. Learn how to configure it.(opens in a new tab)
    Ask your hosting provider to increase the opcache.interned_strings_buffer directive in php.ini, setting it to at least 24.

    Could it be related to the issue?

    Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there,

    Thanks for sharing the details. The Site Health recommendation about the PHP opcode cache and interned strings buffer could potentially affect performance, especially if your site is handling large imports or processing many scheduled actions at once. A small buffer can slow down PHP execution and may lead to timeouts or incomplete imports.

    I recommend reaching out to your hosting provider to increase the opcache.interned_strings_buffer in your php.ini (as suggested, at least 24MB). After that, try importing your historical data again — this often resolves performance-related import issues.

    Once you make this change, if the import still fails or the past-due actions remain high, let us know so we can investigate further.

Viewing 6 replies - 16 through 21 (of 21 total)

You must be logged in to reply to this topic.