Handcrafted Beautiful Bootstrap HTML Templates for your Business Website.
Open Tools → Site Health on many WordPress sites and you’ll find one of these:
Most site owners shrug and move on, because the site looks fine.
On a WooCommerce store, that’s a mistake. Loopback requests and scheduled events are how WordPress and WooCommerce run background work: order emails, subscription renewals, stock updates, analytics imports, webhook deliveries, cleanup jobs. When loopbacks fail, that work can silently stop. Your storefront keeps working while the machinery behind it stalls.
This guide explains what a loopback request is, what fails in WooCommerce when it doesn’t work, the common causes, and how to fix it properly.

A loopback request is your website making an HTTP request to itself: WordPress on your server calling https://yourstore.com/wp-cron.php (or another URL on your own site) over the network.
WordPress uses this to run tasks in the background, without making a visitor wait. When a page loads, WordPress checks whether any scheduled tasks are due. If they are, it fires a quick loopback request to wp-cron.php, which runs those tasks in a separate process.
WooCommerce builds on this with Action Scheduler, a queue for background jobs. Action Scheduler is triggered by WP-Cron and also uses asynchronous requests to keep the queue moving.
So if your site can’t reach itself, or WP-Cron is switched off without a replacement, background work doesn’t run.

| Background job | What you notice |
|---|---|
| Deferred or queued order processing | Orders stuck mid-flow; some payment confirmations processed late |
| Transactional emails that depend on queued work | Customers don’t get confirmations promptly (guide) |
| Subscription renewals | Renewals not created or not charged on time (guide) |
| Analytics imports | WooCommerce Analytics looks empty or out of date |
| Outgoing webhooks to other systems | ERP, fulfilment or CRM integrations stop receiving orders |
| Scheduled sales and coupon expiry | Sales don’t start or end on time |
| Unpaid order cancellation and cleanup | Timers don’t run on schedule |
In WooCommerce → Status → Scheduled Actions, the tell-tale sign is a Pending tab full of actions whose scheduled time has already passed: hundreds of past-due actions.
Your server calling itself can look like an attack: a request from a data-centre IP (your own) with no browser. Host firewalls, security plugins and CDN bot protection sometimes block it. Ironically, the same rules often block payment webhooks too. (Firewall blocking webhooks)
Staging sites are often protected with HTTP basic authentication. If that protection is left on a live site, or the site was pushed live from staging with it, every loopback request gets a 401.
The server must resolve your domain and complete an HTTPS connection to itself. A mis-set hosts file, a domain pointing elsewhere (behind a CDN or during a migration), or an SSL certificate the server doesn’t trust produces timeouts or “cURL error 28” messages.
Site Health gives loopback requests around 10 seconds. A plugin that makes every request slow (heavy session handling, external API calls on every page) can make loopbacks time out. A WordPress.org thread traced loopback and REST API timeouts on a WooCommerce site to one plugin’s session handling. Changing its settings resolved it.
DISABLE_WP_CRON without a replacementMany hosts and performance guides set define( 'DISABLE_WP_CRON', true ); in wp-config.php to stop WP-Cron running on page loads. That’s good practice, as long as a real server cron job runs WP-Cron instead. If nobody set up that server cron (common after a migration), scheduled work simply never runs, and no error appears anywhere.
WP-Cron triggers on visits. On a quiet store, hours can pass with no visitors, so nothing runs. Not a failure as such, but it makes background work slow and unpredictable.
DISABLE_WP_CRON set to true? If so, ask your host whether a server cron job runs wp-cron.php.wp cron test checks whether WP-Cron can spawn; wp cron event list shows overdue events.wp-cron.php.Set up a real server cron (recommended for every store). In your hosting control panel, add a cron job that runs every few minutes:
*/5 * * * * wget -q -O - "https://yourstore.com/wp-cron.php?doing_wp_cron" >/dev/null 2>&1
or, with WP-CLI:
*/5 * * * * cd /path/to/site && wp cron event run --due-now >/dev/null 2>&1
Then set DISABLE_WP_CRON to true so visitors don’t also trigger it.
Allow your server to reach itself. Allowlist your own server IP in your security plugin and host firewall, and exempt wp-cron.php and admin-ajax.php from bot challenges.
Remove basic auth from production, or exempt your server’s own requests from it.
Fix DNS/SSL on the server with your host: the server should resolve your domain to itself and trust the certificate.
Find slow plugins with a conflict test on staging if loopbacks time out.
Let the backlog drain. Don’t delete past-due actions. They can include real customer emails and renewals. Once the cause is fixed, they’ll run. On very large backlogs, ask your host for help, or run wp action-scheduler run in batches.
Then sweep up. Check whether any customers missed confirmation emails or renewals during the stall.
A store moves to a faster host. The migration service copies wp-config.php, including define( 'DISABLE_WP_CRON', true );, which the old host required because it ran a server cron job. Nobody sets up a cron job on the new host.
Site Health had been showing “A scheduled event is late” since day 1. Nobody looked.
The fix was a single cron job in the hosting panel. The cleanup took two days: replaying renewals carefully, checking which customers missed emails, and reconciling the fulfilment system.
The worst thing about loopback failures is that they’re silent and slow-burning. Site Health shows a warning once, and nobody looks at Site Health. The backlog grows by the hour.
Ordafide Order Integrity for WooCommerce (free) puts this front and centre on its Store health screen:
DISABLE_WP_CRON is set.wp-cron.php, contacts no other service, and runs only when you press the button.An optional weekly summary email tells you when there’s something to fix. For agencies, wp ordafide health reports the same from the command line.
Ordafide Pro adds real-time alerts (Slack, SMS, email, signed webhook) so a stalled queue reaches you within the hour, and a signed heartbeat endpoint an external monitor can poll to confirm the store’s own checks are still running, which matters when the scheduler itself is the thing that broke.
For most stores, every 5 minutes is a sensible default. Busier stores, or those with lots of subscriptions and integrations, often run it every minute. Very quiet stores can get away with 15 minutes, but emails and renewals will be less punctual. Whatever you choose, make sure it’s one cron job, not several competing ones, and that visitor-triggered WP-Cron is disabled so the two don’t overlap.
What does "the loopback request to your site failed" mean?
WordPress couldn't make an HTTP request to its own site. Background tasks that rely on that, including WP-Cron and parts of WooCommerce's Action Scheduler, may not run.
Does a failed loopback request affect WooCommerce?
It can. Order processing steps, emails, subscription renewals, analytics imports and outgoing webhooks all rely on background jobs.
Is it safe to disable WP-Cron?
Yes, if you replace it with a real server cron job that runs `wp-cron.php` every few minutes. Disabling it without a replacement stops scheduled work entirely.
Should I delete past-due scheduled actions?
No. Fix the cause and let them run. They may include customer emails and renewals.
How can I monitor WooCommerce background jobs?
Check WooCommerce → Status → Scheduled Actions regularly, or use Ordafide, which shows queue health, scheduler status and a loopback test on one screen.
Can a security plugin cause loopback failures?**
Yes. Firewalls and security plugins sometimes block your own server's requests to wp-cron.php. Allowlist your server's IP and exempt wp-cron.php from bot challenges.
What does "a scheduled event is late" mean?
WordPress noticed a scheduled task that should already have run. One late event can be a blip, but repeated warnings usually mean WP-Cron isn't being triggered reliably.
Does WooCommerce Analytics depend on background jobs?
Yes. Analytics imports order data in the background, so a stalled queue can make reports look empty or out of date while real orders keep arriving.