I found following recommendation for improvements in my WordPress site health status after installing LiteSpeed caching plugin.

The scheduled event, action_scheduler_run_queue, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

Soon after purging cache it disappears but after few minutes again it shows up. Should I concern much about this ? Is there any bad effects of having this recommendation to my site. What should I do for this ? Hope you will help me to figure this out.

Thank you !
Saku Wasan

I then installed the REDIS plugin to enable Object Cache, which sorted that error.

Now I have a new error in SiteHeath.

“A Scheduled Event is Late”

“The scheduled event, jetpack_scan_refresh_states_event, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.”

Obviously, I could uninstall REDIS to correct the issue, but that puts me back to square one!

Any ideas?

I’m not tech savvy, what is the best way to fix this?

The scheduled event, rank_math/sitemap/hit_index, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

How should I fix this?

the WordPress blogs I run do not have auto-updates configured or active and in general writing to the webroot is very restricted.

For the updates this isn’t a big issue as I have scripted the whole process of taking a backup of the DB along with the webroot and even scripted updating plugins and themes.

However, it seems Site Health takes issue with the fact that the webroot is readonly.

The scheduled event, wp_privacy_delete_old_export_files, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

Is there a way I could run these scheduled events Site Health mentions from outside WordPress, e.g. as an actual cron job on the server? And in case that is possible, can I also disable the scheduling for these events inside WordPress?

Thanks and with best regards,

Oliver

Al realizar el Site Health Status me sale el siguiente mensaje:

“A scheduled event has failed. Performance.
The scheduled event, do_pings, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended”

Alguna solución?

Message says:
“The scheduled event, wpephpcompat_start_test_cron, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.”

The error message keeps changing but I think its got something to do with the cron file.
I’m not sure how to fix this. Could someone give me some advice?
Thanks.

Message says:
“The scheduled event, ngg_delete_expired_transients, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.”

I’m not sure how to fix this. Could someone give me some advice?
Thanks.

Message says:
“The scheduled event, ngg_delete_expired_transients, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.”

I’m not sure how to fix this. Could someone give me some advice?
Thanks.

While Checking Site Health Status i have found this .*-

The scheduled event, action_scheduler_run_queue, is late to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

Any Help ??