Hi @pgsmarketing,
Nothing is seriously wrong here. What you’re seeing just means WordPress tried to clean up a scheduled task created by Jetpack Boost (jetpack_boost_preload) and couldn’t save the updated cron list. This is pretty common after a site move or hosting change.
To answer your questions directly:
Is something wrong?
No. This doesn’t affect visitors or the site’s functionality. It’s a cleanup issue, not an active problem.
Can you delete Jetpack Boost safely?
Yes. Since you’re now using LiteSpeed instead, you can safely deactivate Jetpack Boost and delete the plugin. There’s nothing special you need to do before removing it.
About the cron notice
In most cases, once Boost is deactivated or deleted, WordPress stops trying to manage that cron task and the message goes away on its own.
If you still see the warning in your logs after deleting Boost, you can remove the leftover cron entry manually using a tool like WP Crontrol by deleting any jetpack_boost_preload events. That’s optional, just cleanup.
You’d only need to dig deeper if you start seeing similar cron errors for other plugins or scheduled tasks. Otherwise, you’re good to go.
Hope this helps, but if you have any question, let me know.
My concern is that the error log has ballooned by 3800 entries and growing from this problem, and the site has been having some resource usage issues, so it seemed suspicious. It also seems bizarre that the fix is to use another plugin to clean up the problem that the plugin left behind.
However the cron entry can’t be deleted with WP Control (“The cron event list could not be saved.”), so what can be done to remove it? I paused it, but I can’t delete it, and I’d prefer not to have to keep this plugin for this. Thanks.
The best fix I could find was to delete the cron entry from the tables. That solved the issue, so I guess that’s the best solution I can suggest anyone else who encounters the same problem.
Thanks for following up and for sharing what worked.
You’re right, if WordPress can’t save cron changes, deleting the orphaned cron entry directly from the database is a valid fix, and explains why WP Crontrol hit the same error. Jetpack Boost was just the hook triggering it repeatedly.
If you notice similar cron write errors for other plugins or scheduled tasks, that would point to a broader DB or caching issue on the host, rather than anything Boost-specific.
Thanks again for taking the time to report back, it’s helpful context for others too.
