{"id":8597,"date":"2025-11-14T20:26:56","date_gmt":"2025-11-14T20:26:56","guid":{"rendered":"https:\/\/resizemyimg.com\/blog\/?p=8597"},"modified":"2025-11-14T20:30:58","modified_gmt":"2025-11-14T20:30:58","slug":"when-a-hosts-rate-limiting-throttled-wp-cron-and-broke-scheduled-emails-the-offloaded-cron-setup-that-solved-it","status":"publish","type":"post","link":"https:\/\/resizemyimg.com\/blog\/when-a-hosts-rate-limiting-throttled-wp-cron-and-broke-scheduled-emails-the-offloaded-cron-setup-that-solved-it\/","title":{"rendered":"When a Host\u2019s Rate-Limiting Throttled wp-cron and Broke Scheduled Emails \u2014 the Offloaded Cron Setup That Solved It"},"content":{"rendered":"

Everything was fine. Emails were going out. Customers were happy. And WordPress just hummed along\u2026 until it didn\u2019t.<\/p>\n

One day, emails stopped sending. WooCommerce orders went quiet. Newsletter blasts became ghost stories. The problem? wp-cron<\/strong>, the little scheduling engine inside WordPress, got throttled<\/em> by the hosting provider.<\/p>\n

TL;DR:<\/strong> A shared host started limiting background tasks like wp-cron. This broke scheduled emails in WordPress. We fixed it by offloading wp-cron<\/em> to a real cron job on the server. Now everything runs reliably, and emails send right on time!<\/p>\n

Wait… What\u2019s wp-cron?<\/h2>\n

In WordPress, there’s a thing called wp-cron<\/strong>. It’s like a tiny robot that runs scheduled tasks. Post publishing, product updates, backups, and yes \u2014 even sending emails. But here\u2019s the catch \u2014<\/p>\n

Wp-cron only works when someone visits your site.<\/em><\/p>\n

If no one visits, it doesn\u2019t run! And if your host blocks or slows background tasks, wp-cron never runs properly at all.<\/p>\n

The \u201cUh-Oh\u201d Moment<\/h2>\n

We started noticing a problem. Emails weren\u2019t going out. Scheduled blog posts didn\u2019t appear. A developer peeked under the hood and saw a massive backlog of cron events waiting to be processed. Hundreds of them. All stuck.<\/p>\n

We checked the logs and found the culprit: the host was throttling wp-cron<\/strong>. They were blocking or delaying the file wp-cron.php<\/code> to reduce server load. On shared hosting, this is common. It reduces spammy scripts from overloading the system \u2014 but it also breaks WordPress scheduling<\/em>.<\/p>\n

So, nothing was running. Not the WooCommerce emails. Not the post scheduler. Not even plugin updates that relied on cron.<\/p>\n\"\"\n

The Quick Fix That Didn\u2019t Work<\/h2>\n

Our first step? We tried a plugin. A cron management plugin. It showed us the queue and confirmed the issue. We also disabled and re-enabled wp-cron. Then we manually triggered it. Still? No dice.<\/em><\/p>\n

It would run sometimes, then stall again. It wasn\u2019t consistent. The host\u2019s limitations were just too tight. They weren\u2019t evil \u2014 just cautious. Shared servers are shared, after all.<\/p>\n

The Real Solution: Offloading wp-cron<\/h2>\n

That\u2019s when we decided to do the smart thing \u2014 offload wp-cron<\/strong> and set up a real server-side cron job.<\/p>\n

Unlike wp-cron, which depends on site traffic, real cron jobs are handled by the server\u2019s operating system<\/em>. They run like clockwork \u2014 every minute, hour, or whatever you tell them.<\/p>\n

What We Did (Simple Steps):<\/h3>\n
    \n
  1. We disabled the built-in wp-cron system in WordPress.<\/li>\n
  2. We set up an actual cron job on the server.<\/li>\n
  3. It pinged wp-cron.php<\/code> at regular intervals (every 5 minutes).<\/li>\n
  4. WordPress now ran scheduled tasks on time, every time.<\/li>\n<\/ol>\n

    Let\u2019s Break That Down:<\/h3>\n
      \n
    1. Disable wp-cron in WordPress<\/strong><\/li>\n

      Open wp-config.php<\/code> and add this line:<\/p>\n

      define('DISABLE_WP_CRON', true);<\/code><\/pre>\n
      This tells WordPress to stop triggering its internal cron on user visits.<\/p>\n
    2. Add a real cron job in your cPanel or server<\/strong><\/li>\n
      If using cPanel, go to Cron Jobs<\/em> and add this command:<\/p>\n
      *\/5 * * * * wget -q -O - https:\/\/yoursite.com\/wp-cron.php?doing_wp_cron >\/dev\/null 2>&1<\/code><\/pre>\n
      This pings wp-cron.php<\/code> every 5 minutes.<\/p>\n<\/ol>\n
      And just like that \u2014 scheduled emails came back to life<\/em>!<\/p>\n
      Where Offloading wp-cron Really Matters<\/h2>\n