Cron scheduling fails with APCu object cache (could_not_set error)

  • NAROLLES

    (@narolles)


    1 month, 4 weeks ago

    Hello LiteSpeed team,

    I’m using LiteSpeed Cache for WordPress with Object Cache enabled (APCu).
    On my site (WordPress 6.8.3, PHP 8.4.4 LiteSpeed), I get repeated cron scheduling errors:

    [30-Sep-2025 23:39:58 UTC] Error rescheduling event for hook bb_bg_log_clear – could_not_set
    [30-Sep-2025 12:08:04 UTC] Error rescheduling event for hook automator_userspost_posts_published – could_not_set
    [30-Sep-2025 13:26:47 UTC] Error rescheduling event for hook action_scheduler_run_queue – could_not_set
    [30-Sep-2025 15:59:17 UTC] Error unscheduling event for hook jetpack_scan_refresh_states_event – could_not_set
    [01-Oct-2025 05:29:44 UTC] Error rescheduling event for hook jetpack_sync_full_cron – could_not_set

    It seems that update_option('cron') fails to save when APCu object cache is active.
    Option size is small (11 KB), so not corrupted.

    Questions:

    1. Can LiteSpeed Cache exclude specific WordPress options from object cache (like cron, doing_cron, action_scheduler_lock_async_request_queue)?
    2. Do you recommend disabling APCu for cron events?
    3. Is there a known workaround for this under PHP 8.4 + LiteSpeed + APCu?

    Thanks,
    Luc Narolles – JAF-info

You must be logged in to reply to this review.