Cron error, automatic updates not working

  • Michelle

    (@trainwithchelle)


    5 days ago

    I’m getting a couple of errors on my dashboard that I don’t know how to fix. The first one has been there for over a year about imagick, I still have no idea what it means but it’s not effecting anything. This new one is about a cron job (I think) not performing properly, and it’s preventing my plugins from updating. How do I fix this?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Rachid Braymi

    (@rachidbray)

    4 days, 23 hours ago

    Hi @trainwithchelle ,

    The Imagick warning is optional, if your images are uploading and displaying fine, you can ignore it. Enabling it requires a hosting-level change anyway.

    The real one to address is action_scheduler_run_queue. Worth noting, this isn’t a core WordPress cron event, it belongs to the Action Scheduler library, bundled with plugins like WooCommerce or AutomateWoo.

    1. Do you have WooCommerce or any automation plugin installed?
    2. Who is your hosting provider, and are you on shared hosting, a VPS, or managed WordPress?
    3. Do you have this in your wp-config.php: define('DISABLE_WP_CRON', true);

    Answers to these will narrow it down quickly.

    Thread Starter Michelle

    (@trainwithchelle)

    4 days, 23 hours ago

    @rachidbray

    1. No WooCommerce or automation plugin
    2. Hosting with IONOS, shared maybe?
    3. I never added that code

    The only thing that has changed is that I’m now using a booking software plugin (LatePoint), it seems the issue started shortly after that.

    Rachid Braymi

    (@rachidbray)

    4 days, 13 hours ago

    @trainwithchelle
    Timing clearly points to plugin
    To confirm, temporarily deactivate LatePoint, then go to Tools → Site Health → Status, wait a few minutes and refresh the page; let me know if the “scheduled event failed” message disappears or is still there, this will confirm whether LatePoint is causing the issue without needing any technical steps.

    Thread Starter Michelle

    (@trainwithchelle)

    3 days, 17 hours ago

    @rachidbray I deactivated it and waited as suggested, the error was still there.

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

You must be logged in to reply to this topic.