Skip to content
KAZCODE Universal Storage KAZCODE Universal Storage

Cron & Background Jobs

How background jobs run

Background work (offload, migration batches, cleanup) runs through a queue that prefers Action Scheduler when it’s available on your site, and falls back to WordPress’s own cron-based queue when it isn’t.

Symptom: jobs seem stuck or slow

  1. Check Universal Storage → Dashboard for the current background job status.

  2. If your site relies on WordPress’s default “visit-triggered” cron (no real server cron configured), background jobs only advance when something visits the site — a low- traffic site (or staging environment) can appear “stuck” simply because cron isn’t firing often.

  3. Prefer WP-CLI for anything you need to run reliably and immediately, independent of whether cron fires:

    Terminal window
    wp universal-storage migrate --batch-size=100
    wp universal-storage queue status

If Action Scheduler is active

Check Action Scheduler’s own admin screen (under Tools, if the plugin/library exposes one on your site) for pending/failed scheduled actions related to Universal Storage’s job handlers.

Verify it’s resolved

wp universal-storage queue status reports the current queue state without depending on cron/Action Scheduler timing at all.