The scheduled event, jetpack_scan_refresh_states_event, is late to run.

I have the same problem as well.

Hi there, @paul,

Thanks for reporting this, and sorry for the trouble!

Could you post your site URL here, so I can have a look?
?
If you want it to remain private, you can also contact us via this contact form:
Contact Support

****
@afrehdo, thanks for reporting this too. Could you please start your own thread, as per the Forum Welcome?
https://www.ads-software.com/support/plugin/jetpack#new-post
?
Thank you!

https://paulbeard.org/wordpress will do it. Site health is very slow to load, another artifact of 6.x.

Hi @paul –

Thanks for sharing the URL. I ran an operation on our end that may help with this.

However, something to keep in mind is that cron in WordPress only runs when a page is requested:

https://developer.www.ads-software.com/plugins/cron/

It looks like your site doesn’t have very many visits, which I think will cause the job to be delayed.

Interesting…I see some traffic/page requests.

grep -c wordpress /var/log/httpd/httpd-access.log
255

Is this variant on cron a new thing? Seems like cron, read as a function of time for the execution of jobs, is not a great name. System cron runs even w no users logged in where this is driven by user interaction and not all that accurately even then. Not sure this explains why the site health page loads to slowly or why I needed to install two different caching methods to turn off warnings about them. On the one hand WP is not running jobs due to what it perceives as a low page requests but on the other, it squawks about the need for caching to improve performance/responsiveness?

I think the performance/responsiveness issues are baked in. These are new with 6.x. This system is lightly loaded and shouldn’t have any issues returning pages. If there are issues in the stack (maybe php-fpm or mariadb or nginx need some tuning?) it would be useful to have some tips in resolving those.

Not sure this explains why the site health page loads to slowly or why I needed to install two different caching methods to turn off warnings about them. On the one hand WP is not running jobs due to what it perceives as a low page requests but on the other, it squawks about the need for caching to improve performance/responsivenes

I’m not sure that the delayed job is related to the slow Site Health or the caching issues. That sounds like something unrelated to Jetpack.

Could you try disabling the cache plugins to see if that allows the job to run?

It was slow before I installed the caching methods so I will assume it will still be slow if I remove them. If I see the error again, I can try it. I just looked and Site Health passed all tests. Unusual.

If I see the error again, I can try it.

Thanks. Please let us know what you find.

Hi @paul, just checking in here to see if you have any updates?

Inconclusive. The dashboard showed three critical errors but when the detail page loaded it was all clear.

Hi @paul – I’m not sure if it is related, but I saw that it has been some time since your site has run a sync with WordPress.com. I’ve kicked one off to see if it might clear some things up for you.

Hey there, @paul,

It’s been one week since this topic was last updated. I’m going to mark this thread as solved. If you have any further questions or need more help, you’re welcome to open another thread here. Cheers!