#230 –  A scheduled event is late

Hi to the WeeblrPress team,

On WordPress I get this message:

A scheduled event is late

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

Any idea where should I look to solve this problem?
website: https://veryprivategallery.com/

Best

Hi

Hard to say where it's coming from. It means that the weeblrAMP task that's checking for weeblrAMP updates have not run at the expected time. It does not mean they failed, simply that your WordPress site did not run them for some reason. And the new Site health feature identify that.

Things to look at are:

- are there other similar messages, for other plugins or tasks?
- do you have any error message in your PHP error log file that relates to cron or weeblrAMP?

Best regards

Hi again

Another thing to look at is actually whether you have setup a real CRON job or are just using the native WP cron. That would mean scheduled tasks are triggered by visitors visiting your site pages. As such, depending on site traffic, it's rather easy for WP to miss some scheduled tasks.

Best regards

Thank you for the answers.

Yes, it seems it is a CRON problem but I am not sure how to solve it. Only Weeblramp is impacted, it seems and it causes long delay on page speed insights just for AMP.

Certificate verification disabled (sslverify=false)
https://veryprivategallery.com/wp-cron.php
?doing_wp_cron=1598007724.6726119518280029296875

spawn_cron()
wp-includes/cron.php:729
wp_cron()
wp-includes/cron.php:774
do_action('init')
wp-includes/plugin.php:478

Do you think the Hosting support could help on this? Or do you have any hint about solving it? Because online I can see the solution to make a local CRON and disable WP CRON but it seems difficult

Hi

it seems and it causes long delay on page speed insights just for AMP.

What does page speed insight has to do with cron jobs? exactly what do you do and what do you measure to say that "it causes long delay..."?

Best regards

You are right. Nothing tells me that it is the origin of the delay. Sorry.
Simply I have Speed Delay on AMP version of my posts, and I have this problem related with WeeblrAMP indicated on WordPress.
I am just trying to solve the problem here.

Hi

Simply I have Speed Delay on AMP version of my posts

Again, what is that? where and how do you see a "delay"? I cannot guess what you are doing and every bit of information is important.

Best regards

Hi,
I still need to improve my speed optimisation but for example, on Page Speed Insights the Instagram article is slower on AMP (mobile) than on Mobile version.
https://veryprivategallery.com/instagram-tips-for-artists/ here
https://veryprivategallery.com/instagram-tips-for-artists/amp there

The Speed Index is bigger for the responsive is 4.0 (average) and on AMP is 5.0
and it says "Reduce initial server response time" 1.5 sec for amp while it doesn't have this problem on the mobile responsive version.

Then I used "Delay" and this is my mistake (by analogy) because of the term "late", my bad
"The scheduled event, check_plugin_updates-weeblramp/weeblramp.php, is late to run"

Hi

Page Speed Insights the Instagram article is slower on AMP (mobile) than on Mobile version.

Page speed insight cannot be used on AMP pages, it does not take into account the fact that pages are cached.

Page Speed Insights the Instagram article is slower on AMP (mobile) than on Mobile version.

This might be the case but it does not matter with AMP as the pages are cached by Google and Bing and displayed instantly.

Then I used "Delay" and this is my mistake (by analogy) because of the term "late", my bad

"The scheduled event, check_plugin_updates-weeblramp/weeblramp.php, is late to run"

So there's no relationship between this and the fact the Page Speed may find your page slower. The check_plugin_updates is something that happens once on a while, not when rendering pages. It will actually happen and be triggered by any page on your site, AMP or not.

The only reason a cron job could be late is if there's not enough visits on the site to trigger it before the date and time it was scheduled. This does not denote an issue with the plugin itself, only that your crons are not running often enough.

Note that the fact you only see weeblrAMP listed there only means that you probably don't have many scheduled tasks on your site.

A definitive fix is indeed to have a real CRON set up. As this will be triggered by your server, I suspect your hosting company can help. If you ask them assistance in setting up a "cron for WordPress", I'd suspect they'll be very familiar with that.

Lastly, this message will not affect weeblrAMP operation in any way.

Best regards