• Resolved aiosa

    (@aiosa)


    I am seeing tons of the same log trying to run a cron job. This issue appeared after migration of our multisite wp. The linked website is irrelevant, as I don’t know which blog the logs are comming from (and I don’t think it’s that important either). The error happens perriodically in between every 1 second up to a few minutes and states (translated):

    [29-Oct-2023 13:40:42 UTC] Error in cheduled event Cron for hook: woo_smart_cron_hook, Error code: invalid_schedule, Error message: Schedule does not exist., Data: {“schedule”:”every_twelve_hours”,”args”:[],”interval”:43200}

    Since it does not affect the behavior we have been ingoring it for some time solving other issues, but now I would like to get rid of it. I could not find anything related to this particular job, so I need a help with solving this. Thank you.

    • This topic was modified 2 years, 5 months ago by aiosa.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Support Shameem – a11n

    (@shameemreza)

    Hi @aiosa

    The error message you’re seeing suggests that the schedule every_twelve_hours does not exist. This could be because the cron schedule was not properly set or migrated.

    To resolve this, you can try to set up the cron schedule manually. You can use the wp_schedule_event function to do this. Here’s an example of how to do it:

    if (!wp_next_scheduled('woo_smart_cron_hook')) {
    wp_schedule_event(time(), 'every_twelve_hours', 'woo_smart_cron_hook');
    }

    You can add this code to your child theme’s functions.php file. Please remember to replace every_twelve_hours with the correct interval that you want to use.

    If the issue persists, it might be a plugin or theme conflict. Try disabling all plugins except WooCommerce and switching to a default theme like Storefront or Twenty Twenty-Three to see if the issue still exists.

    Please let us know if this helps or if you need any further assistance.

Viewing 1 replies (of 1 total)

The topic ‘Weird error spamming log’ is closed to new replies.