Site Health Stats – A scheduled event has failed – wp_update_plugins

Hi there!

The issue is likely being caused by how Jetpack uses the WordPress cron system. Can you reach out to your host to have them check to see if cron is enabled and working correctly on your site?
Could you also check your site’s wp-config.php file, and let me know if cron is currently disabled? If it is disabled, you’ll see this bit of code somewhere in that file:
define( 'DISABLE_WP_CRON', true );
Please remove this if it’s present.
Another thing you might try is installing this plugin:
https://www.ads-software.com/plugins/wp-crontrol/
which should let you see if there’s anything wrong with your site’s cron system.

@fresatomica I spoke with my host provider at length. They said that they do not allow the wp_update_plugins to be touched because they control the updates for all WP cure files. GoDaddy Managed WordPress handles all WordPress updates, changes to core files, database, etc. the only thing I’m responsible for is updating plugins I download. They told me the wp_update _plugins is not the one I control. So, going back to my original question then, is that true. Is wp_uodat_plugin where core files are updated? If that’s the case then I guess this scheduled event can’t be fixed? I also really would like to know from the Jetpack team why this is even being checked in their site health check and what’s the specific purpose of this specific scheduled event in regards to that file itself?

We use that for our plugin auto-updater: https://jetpack.com/support/plugin-management/

I am relatively sure that if you don’t have any plugin’s enabled for auto-update, the warning won’t appear.

James Huff (@macmanx) James, I absolutely do not have anything set for auto update. Is there a switch in Jetpack that I’m supposed to make sure of this? As for GoDaddy, they have auto update on for WordPress updates I believe but the six plugins I have I most hit the update button myself, so any help tracking down the source of what is triggering this message would be great! ??

Huh, interesting. Ok, please reach out to us via https://jetpack.com/contact-support/?rel=support so we can take a closer look.

@macmanx I went to that link and it tells me to login. I login and select my picture to continue and it brings me right back to the page that says to login. I tried it on safari and chrome to no success. I’m not exactly sure why I’m supposed to be doing over at that link but it’s not working to log in and process?

That can sometimes happen with these new built-in “intelligent tracking protection” features in some browsers like Safari.

Since we use WordPress.com’s user system, we’re using a WordPress.com logged in cookie on Jetpack.com, and suddenly some browsers think that’s evil.

We’re working on a solution (it doesn’t help that each browser has their own protocol for how they want that to work), but for now temporarily disabling anything like that should work. Once you’ve submitted, support there is all via email, so you only need to do that once.

@macmanx Nothing is working to do that even with me going into a Private browser. Is there an alternative way to do this? I don’t understand why it can’t be done through this here? Is there also some Jetpack feature I should check to see if auto updates is somehow turned on? Does Jetpack normally try to automatically update WordPress updates for the core WP? If so that will trigger this message on Managed WordPress?

We have tools available there which are not available here.

Please send an email to help (at) jetpack (dot) com

@macmanx not “support (at) Jetpack (dot) com?”

Both actually work, help is 3 less characters. ??

@macmanx i just sent an email using the three less character support email. ?? I put your name in the subject line because the last time I opened a ticket on the boards and sent an email Jeremy Herve said that wasn’t proper protocol so i was trying to respect that. Please let me know you see the email I just sent. I also have three other minor tickets that I opened by email that really were just questions waiting to be answered. Do this makes four opened ones unfortunately. Anyway, you never answered if there was a setting on my Jetpack dashboard about updates or in WP that I can check to make sure auto updates isn’t checked somehow?

No available setting for this, we’ll need to figure out why it’s firing.

We’ll reply to the emails as soon as we can.

I got an email rejection to the support email using the help one. It said unknown address. I resent it under support as the beginning and it went through. Just curious, until that message gets resolved, by your team and I, is there a problem that could happen with my site or does that message for Jetpack only indicate that it’s trying to access updates for plugins and it can’t? In other words, is the message’s purpose for core WordPress or plugins only or both and with it being there will it have any negative affect upon my performance? Because the message also mentioned scheduling posts which I found weird since that update_plugin isn’t used to scheduling?

Ugh, the help alias must have broke again, we’ll get that fixed, sorry about that.

Nothing wrong will happen to your site in the meantime, it’s just a warning that shouldn’t be firing.