The scheduled event has failed

After I change my server name to cloudflare, the warning “The scheduled event has failed” appears on the site health of my wordpress site, and if I change it to my original server name, the warning does not appear.
how to overcome it?
Thank you

1 Like

What’s the domain?

2 Likes
1 Like

I see you’re running LiteSpeed. Here is some information:
https://docs.litespeedtech.com/lscache/lscwp/troubleshoot/#a-scheduled-event-has-failed

You might even need to use a cronjob to run WordPress cron events on a regular basis. That’s covered in the “Scheduled Posts…” section of the link I posted above.

3 Likes

What’s the problem with litespeed? because when I use the name of my hosting server, even if I use litespeed, the warning does not appear
And I have disabled the litespeed plugin, but the message still exists

1 Like

Can anyone help ???

Hi
After I change my server name to Cloudflare, the “Scheduled failed event” warning appears on the health of my WordPress site, and if I change it to my original server name, the warning does not appear.
how to handle it?
thank you

1 Like

That is not a cloudflare error message so I suspect that’s why folks are generally unfamiliar with it.

I guess some troubleshooting questions are in order:
Is that the complete message that is displayed?
Can you attach a copy of the error?
Any indication of this error in the logs?
Are there any cron processes running/expected to run that are failing?

Next, perhaps refine some troubleshooting steps. As opposed to changing name servers, does the error still occur/appear if you pause cloudflare on the site (from the overview tab of the cloudflare dashboard). What if you resume cloudflare and click the :orange: on your A and CNAME records to turn them :grey: or DNS only, does the error still occur?

2 Likes

The full text is:
1 critical issue

Your site cannot complete the loopback request
Loopback requests are used to run scheduled events and are used by default editors so that themes and plugins can verify code stability.

Loopback requests to your site failed, this means that loopback-related features are currently not working properly.
Error: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)

1 recommended improvement

Scheduled failed event
The scheduled event, smush_check_for_conflicts, failed to run. Your site is still functioning, but this indicates that scheduled publishing or automatic updates may not function as it should.

Likewise, when I send a newsletter the message is not sent. And also when I scan a site using wordfence it can’t

But when I change the server name from Cloudflare to the name of my host server, the warning does not appear and other plugins can run as they should

Why did it happen? And how to overcome it?
Thank you very much

1 Like

I also got this message from the newsletter plugin:

CDN warning

If you have a CDN active (for example Cloudflare), the service could cache the calls to wp-cron.php totally blocking the WordPress scheduler. Please, be sure to add an exception for this file in your CDN configuration (or ask the provider to add it for you).

How to solve it?
Thank you

1 Like

Can anyone help?

1 Like

This topic was automatically closed after 31 days. New replies are no longer allowed.

Hi
I’ve created a topic here: The scheduled event has failed and nobody answered after some time, so the topic was closed automatically
Can anyone solve it?
Thank you very much

1 Like

Probably the same questions - can you attach a screen shot copy of the error?"

Again, we may be able to help troubleshoot this if you pause cf (but don’t change the nameservers) as:

Hi
This link is a screenshot: http://prnt.sc/u2xaib
I have paused my site from Cloudflare and the problem still appears, but if I change the server name to my host the warning doesn’t appear
Why?

Hello,

Thanks for the details - I’ve responded to you in the Support ticket with some further questions.

Please reply in the Support ticket as the questions I’ve asked may include your private configuration information.

Much appreciated!

1 Like

Hi
I’ve created a support ticket before, but the problem hasn’t been resolved yet.
So am I just waiting for my previous support ticket or am I creating a new ticket?
Thank you

nano /etc/hosts

Set

127.0.0.1 example.com
127.0.0.1 www.example.com
127.0.0.1 subdomain.example.com

Next, use WP CLI to set Cron Job. Depending on hosting instructions may vary. Talk to Sysadmin who is managing your server.

1 Like

What do you mean “nano / etc/hosts”?
And whose IP address is this: 127.0.0.1?
And what is WP CLI?

That instructions is for unmanaged server.

Either way, this is not related to Cloudflare. Regarding your WordPress Cron Job failure issue, you need to talk with host.