You set an import to run every hour, and the next morning nothing has changed: no new job, and the “Next run” time is already in the past. Almost always the schedule is fine and WordPress simply never got the signal to run it. Scheduled jobs in Import Export by RockStarLab are started by WP-Cron. Below, the most common failure is reproduced on a test site, with the fix.
Free: schedules and everything in this guide are part of the free plugin.
Short Answer
- Open Import Export by RockStarLab → Schedules. If Next run is in the past and Jobs Log has no new job, WP-Cron isn’t running.
- Look in
wp-config.phpfordefine( 'DISABLE_WP_CRON', true );. If it’s there, something else must start WP-Cron. - Add a server cron job that runs WordPress’s due events every few minutes, for example
*/5 * * * * cd /path/to/wordpress && wp cron event run --due-now.
How WP-Cron starts scheduled jobs
WordPress has no clock running in the background. WP-Cron checks for due tasks when someone loads a page, and runs the ones whose time has come. A schedule in the plugin is such a task: at its time it creates a new job from the source job, and the job then runs in steps, also through WP-Cron. If WP-Cron never fires, the schedule waits, without an error.
What it looks like
We scheduled an hourly import, “Daily menu import”, and turned WP-Cron off on the site, the way many hosts do. At 21:34 the Schedules page still showed a next run of 21:33 and the last job from the previous hour:

We opened the home page to make sure it wasn’t just a quiet site: still no new job. WP-CLI showed the task waiting:
$ wp cron event list --fields=hook,next_run_gmt,next_run_relative
rsl_ie_process_queue 2026-11-09 21:32:02 now
rsl_ie_run_job_schedule 2026-11-09 21:33:00 now
“now” means the task is due and waiting for WP-Cron.
The usual causes
- WP-Cron is disabled.
DISABLE_WP_CRONis set to true inwp-config.php, often by the host or a performance plugin, but no server cron replaces it. This is what we reproduced above. - The site can’t call itself. WP-Cron starts the work with a request to
/wp-cron.phpon your own domain. A firewall, a security plugin, a password-protected staging site or a broken SSL certificate can block it. Tools → Site Health reports this as a problem with loopback requests or scheduled events. - Nobody visits the site. A staging site or a new site with no traffic has no page loads to trigger WP-Cron, so jobs run late or only when you log in.
- The schedule itself. The schedule is paused, or its source job was deleted. The Status column on the Schedules page shows this.
If the job does start but fails, that’s a different problem: open the job in Jobs Log to see why. For imports from a URL, a run where the file can’t be downloaded shows the reason on the Schedules page and is tried again at the next run (see scheduled imports from a URL).
The fix: a real cron job
With WP-Cron disabled, run WordPress’s due tasks from the server. We ran the command by hand first:
$ wp cron event run --due-now
Executed the cron event 'rsl_ie_run_job_schedule' in 0.012s.
…
Success: Executed a total of 4 cron events.
The schedule created job 97. The job itself runs through WP-Cron too, so the next run of the same command processed it, and it finished. The Schedules page now showed the new last run and the next run an hour later:

To do this all the time, add it to the server’s crontab (in cPanel: Cron Jobs) every five minutes, or every minute for large imports that run in many steps:
*/5 * * * * cd /var/www/html && wp cron event run --due-now > /dev/null 2>&1
Without WP-CLI on the server, a cron job can request https://your-site.com/wp-cron.php?doing_wp_cron instead, for example with wget -q -O - … > /dev/null. Keep DISABLE_WP_CRON set to true once the server cron is in place, so visitors don’t trigger it as well.
Run a schedule right now
While you sort out cron, you can run a schedule’s job immediately with wp rsl-ie schedule run <id> (see the WP-CLI guide). It runs the job in the same process, doesn’t wait for WP-Cron and doesn’t change the schedule’s next run.
Before you change cron settings
Editing wp-config.php or the server crontab affects every plugin that uses WP-Cron. Back up the site and keep a copy of wp-config.php before you change it.
With an AI agent
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) can check whether your schedules are on time:
Did the Daily menu import run this hour?
In our run, after the fix, the agent called rsl-ie/schedule-list. It returned the schedule with last run 21:34:47, last job 97 and next run 22:33, so the run had happened. A next run in the past with an old last job means WP-Cron didn’t start it.
FAQ
Why does my schedule run only when I log in?
WP-Cron runs on page loads. With little traffic, your own visit is what starts it. Add a server cron job.
How often should the server cron run?
Every five minutes is enough for most sites. Use every minute if large imports should finish quickly, because jobs run in steps.
Is it safe to set DISABLE_WP_CRON?
Yes, if a server cron runs wp cron event run --due-now or wp-cron.php regularly. Without one, nothing scheduled will run.
Can I start a schedule by hand?
Yes, with wp rsl-ie schedule run <id>. It doesn’t change the next run.
Where do I see why a scheduled job failed?
In Jobs Log, under the job’s details. Download errors of URL imports also show on the Schedules page.
Related Guides
- Automatic WordPress Import from a URL on a Schedule
- WordPress Jobs Log: Check, Retry and Schedule Imports & Exports
- How to Schedule Recurring WordPress Exports to CSV
- WP-CLI Import and Export for WordPress: CSV, Excel and Cron Scripts
Get the free plugin on WordPress.org.

Comments 0
Have a question or a tip to share? Leave it below.