WordPress Cron Reschedule Error – action_scheduler_run_queue could_not_set

  • tendersleep

    (@tendersleep)


    2 days, 21 hours ago

    Cron reschedule event error for hook: action_scheduler_run_queue, Error code: could_not_set, Error message: The cron event list could not be saved., Data: {“schedule”:”every_minute”,”args”:[“WP Cron”],”interval”:60}

    We are repeatedly seeing the following WordPress cron error in our WP ENGINE logs:

    Error:
    Cron reschedule event error for hook: action_scheduler_run_queue

    Error code: could_not_set

    Error message:
    The cron event list could not be saved.

    Data:
    {"schedule":"every_minute","args":["WP Cron"],"interval":60}

    The issue is occurring repeatedly and we would like assistance identifying the underlying cause. In particular, we would like you to check whether this could be related to:

    The website is hosted on WP Engine.

    Could you please investigate why this error occurs

    We would also appreciate confirmation on whether this error can impact WooCommerce scheduled actions, order processing, emails, subscriptions, webhooks, or other scheduled tasks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Moderator threadi

    (@threadi)

    2 days, 21 hours ago

    Action Scheduler is not part of WordPress. It comes bundled with various plugins or can be installed separately. You mentioned WooCommerce. This library also ships with WooCommerce, so I’d recommend reaching out to their support forum: https://wordpress.org/support/plugin/woocommerce/

    marcio93

    (@marcio93)

    2 days, 19 hours ago

    Hi @adityajain23,

    Regarding the Action Scheduler error on WP Engine: this error (‘The cron event list could not be saved’) typically happens when the wp_options table record for ‘cron’ exceeds MySQL packet limits or gets locked during concurrent cron executions under high-frequency schedules.

    On WP Engine environments, WP-Cron is often executed via alternate runner or system crontab. You can check if the ‘cron’ option row has grown too large or if object caching (Redis/Memcached) is dropping transient cron writes. Running Action Scheduler batches via WP-CLI (‘wp action-scheduler run’) can bypass the WP-Cron lock and prevent queue congestion.

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

You must be logged in to reply to this topic.