WP CRON issue since i’ve deleted all transient

Sure. i’ve tried delete some jobs, so the hours can be change, but take a look at the hours scheduled and the hours of my pc

screen

Those cron times may be inconsistent with your PC as they’re based on the time on the host server.

The thing is, my cron event is now gone so can’t be affecting any runs (not that it should anyway – it runs once a day, so if it fails, it will only affect that run. The hourly runs won’t be affected by my event).

So, we’re back to why you’ve had issues and I can’t tell. It may be a more general issue with your cron – WordPress is notoriously fickle when it comes to WP Cron, as it’s reliant on visitors to your site to ensure that things are kicked off (which is why so many people report issues with scheduled posts not publishing at the right time).

Why it should have gone wrong after installing my plugin, I don’t know. My cron doesn’t appear to be the cause. If it’s the housekeeping of transients that’s the cause, then you have a deeper issue – transients are intended to be temporary data storage. If removal of any of those has affected your cron runs then it may be because something else is (incorrectly) reliant on the data. I would suggest standard diagnostics now – disable all your plugins to see if this rectifies your cron issues (if not, it’s your core installation or hosting). Then enable each plugin at a time and re-test.

Dear David,

thank you very much for your help.

I’m going to hire a developer to investigate further this issue.

Acctually, i’ve fix the cron issue disabling WP CRON by wp-config.php and activating CPANEL CRON.

However, the “housekeep_transients” is still scheduled once a day, even if i have disabled and deleted your plugin.

Have you got any advice to how interrupt the “housekeep_transients” to be scheduled every day?

View post on imgur.com

Hmm, I suspect that cron manager you were using was just displaying the next run and not the event that’s scheduling it. So your previous deletion of housekeep_transients probably only stopped the next run.

Your best bet is to re-install and enable my plugin, then go into the settings and turn off the automatic run – this should remove the cron event completely. Then you can safely remove it again.

Theoretically, however, that cron event remaining shouldn’t cause an issue – it will just try to run some non-existent code and continue peacefully. I think the problems you’re seeing are unrelated.