Jetpack error logs

  • Resolved wpuser

    (@forinn)


    1 year, 2 months ago

    These errors started to appear out of nowhere. Is this something that is being addressed in a next update?

    [30-Dec-2024 14:12:13 UTC] Cron unschedule event error for hook: jetpack_scan_refresh_states_event, error code: could_not_set, error message: The list of cron events could not be saved., data: {"schedule":false,"args":[]}

    Notice: Function Automattic\Jetpack\Assets::alias_textdomain was called incorrectly. Textdomain aliases must be registered before the wp_default_scripts hook. This message was triggered by the woocommerce-analytics domain. Please see Debugging in WordPress for more information. in /home/mywebsite/public_html/wp-includes/functions.php on line 6114
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Alin (a11n)

    (@alinclamba)

    1 year, 2 months ago

    Hi @forinn,

    Thank you for reporting this.

    The errors you’re seeing are related to WordPress Cron tasks and a WooCommerce analytics issue. For the Cron error, please check your site’s Tools > Site Health for any issues with Cron tasks. For the WooCommerce notice, ensure that all plugins are updated.

    Please share the findings with us so we can assist further if needed.

    Thank you!

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    1 year, 2 months ago

    Hi there, @forinn,

    Do you have updates about that, do you still need help? We usually close inactive threads after one week of no movement, but we want to make sure we’re all set before marking it as solved. Thanks!

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

The topic ‘Jetpack error logs’ is closed to new replies.