Why Have My Background Jobs Not Run Yet?

The task is queued, not failed. WordPress runs background jobs through WP-Cron, which only fires when someone visits your site and works through tasks in order, so on a quiet, cached or busy site a job can wait many minutes. Press Run now in the notice, or give WordPress a real server cron.

What happened

Blaze AI Discovery runs its heavier work in the background: the first store audit, product scoring in small batches, the monthly AI-visibility refresh and the feed rebuild. It hands those tasks to WooCommerce’s Action Scheduler, which runs them through WP-Cron.

WP-Cron is not a real cron. It only fires when someone visits your site, and it processes tasks in order. On a quiet site, a site behind a full-page cache, or a site with a long backlog of tasks from other plugins, a job can wait a long time before its turn. That is what the dashboard is telling you.

What to do

• Run now. The button in the notice runs the due tasks immediately. It is safe to press more than once.
• Check the queue. WooCommerce → Status → Scheduled Actions, search for blazeaid. Pending with an old date means WP-Cron has not reached it; Failed shows the error in the log column.
• Give WordPress a real cron. This is the permanent fix and it helps every plugin on the site, including WooCommerce’s own emails and stock jobs:
  1. Add define( 'DISABLE_WP_CRON', true ); to wp-config.php.
  2. Ask your host for a system cron that requests https://your-store.com/wp-cron.php?doing_wp_cron every minute (or runs wp cron event run --due-now). Most managed WordPress hosts already do this; on cPanel or Plesk you add it under Cron Jobs.
• Exclude wp-cron.php from page caching. If a caching plugin or CDN serves it from cache, the request never reaches PHP. LiteSpeed Cache, WP Rocket and Cloudflare all have an exclusion list for this.

If WP-Cron is disabled

If DISABLE_WP_CRON is already true and there is no server cron behind it, nothing runs in the background at all. The dashboard says so explicitly in that case. Either remove the constant or add the server cron above.