WordPress Site Health – bpsPro_AFS_check failed to run

[Rami M]

Upon running new WordPress Site Health check, I see this message under “Recommended improvements”:

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

Thanks

[AITpro Admin]

Yep, we are aware of this issue with BPS Cron Jobs and WordPress Site Health.  We see this message below regularly.  We are not sure why the cron jobs are being detected as a “problem” since they are not actually problems.  My guess would be that WordPress Site Health checks to see if a cron job ran last, but BPS Crons don’t necessarily need to run at every scheduled event time.  Example:  The Security Log check cron job checks the size of the Security Log file and will only zip, email and replace it if needed.  In any case, this is nothing to be concerned about.  If there is a problem in BPS then BPS will display an alert or send you an email.  It would be nice if WordPress Site Health added an additional option to ignore these messages.

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

[Rami M]

Makes sense 🙂 Thanks for your help.

[Jarde]

[Forum Reply has been merged into this relevant Topic]

I seem to have some kind of server conflict or bug with with Bps pro.  Site health shows that timed event is late or not run.  It`s always some Bps pro timed event; bpsPro_AFS_check or bpsPro_HPF_check. Using latest WordPress.  I already deactivated all other plugins (for testing) except Bps pro and problem still persists. So it seems to be not plugin compatibility issue. Using latest Bps pro.

What steps to take to solve problem ?

[AITpro Admin]

@ Jarde – You can ignore the WordPress Site Health warning.  See the explanation above in this forum topic.

[Jarde]

@AITpro Thanks.

[AITpro Admin]

As it turns out there was a conditional logic flaw in some BPS Cron jobs.  These bugs have been fixed in BPS Pro 14.7/BPS 4.2.  BPS Pro 14.7/BPS 4.2 will be released in a few days.  Note: In some cases I have noticed that WP Site Health appears to have an additional issue/bug.  Example: Scheduling a new Cron Event and then immediately checking the WP Site Health page displays an error  – “The scheduled event, xxxxxxx, is late to run…”.  I’m assuming there is a glitch somewhere in the WP Site Health code. In any case I did find bugs in some BPS Cron jobs when certain BPS option settings were chosen. So that is now fixed anyway, but yeah WP Site Health is unfortunately still going to randomly display this “error” > “The scheduled event, xxxxxxx, is late to run…”. The “error” can be ignored because there is not actually a problem occurring with BPS Cron jobs.

[Author]

Posts