You start a big import, it climbs to 20 or 30 percent, and then the number stops moving. Often nothing has failed: the import is waiting for WordPress to give it time to run. Below: why that happens with Import Export by RockStarLab, how to tell a waiting import from a broken one, and three ways to finish it without duplicates. We tested it with a 5,000-row CSV of a coffee roastery’s cupping notes.
Free: everything here works in the free plugin. PRO: the same applies to PRO imports such as WooCommerce products and orders.
Short Answer
- Open Jobs and reload it twice. If the job says Processing and the item count doesn’t change, it is waiting, not broken.
- Finish it: click Continue next to the job (version 2.1.42 and later), visit the site so WP-Cron runs, set up a server cron job if your host has WP-Cron turned off, or run
wp rsl-ie job wait <id>with WP-CLI. - The import continues from the next row. Rows that were already imported are not imported again.
Why an import stops at a percentage
The plugin imports in batches. While the progress page is open, your browser requests the next batch as soon as the last one is done:

When you close the tab, the job keeps going in the background with WP-Cron. WP-Cron isn’t a real timer: WordPress runs it only when someone loads a page of the site. Two things can stop it:
- No visitors. In our first test, we closed the tab at 26%. The job reached 1,750 of 5,000 rows and stayed there for as long as nobody opened the site. As soon as we opened the admin, it carried on and finished.
- WP-Cron turned off. Many hosts add
define( 'DISABLE_WP_CRON', true );towp-config.phpand are supposed to run cron from the server instead. If that server job is missing, background work never runs. In our second test, with WP-Cron off, we closed the tab at 1,050 rows (21%). The job stayed at 21% through every reload of the admin.
How to tell it is stuck

- Status Processing, the same Items count after two reloads a minute apart: the job is waiting for WP-Cron.
- Status Completed with “Failed: N”: the import finished, and some rows had errors. Open the job’s details (the eye icon) to see which rows and why.
- Status Failed: the job itself stopped because of an error. The job details show the reason.
Rows with errors don’t stop an import. The plugin records the error and moves to the next row.
Fix 1: let WP-Cron run
If WP-Cron is on, open any page of the site or keep the Jobs page open and reload it now and then. Each page load lets WordPress run the next batches. In our first test, opening the Jobs page was enough: the job went from 35% to completed.
Fix 2: run cron from the server
If your wp-config.php has DISABLE_WP_CRON set to true, ask your host for a cron job that calls wp-cron.php every minute, or add it in your hosting panel:
* * * * * curl -s https://www.example-roastery.com/wp-cron.php?doing_wp_cron > /dev/null
That runs background imports, scheduled imports and every other plugin’s scheduled tasks, whether or not anyone visits the site. Our guide to scheduled imports that don’t run covers WP-Cron in more detail.
Fix 3: finish it with WP-CLI
If you have SSH access, WP-CLI runs the job in your terminal until it is done, without WP-Cron. Use the job ID from the Jobs page:
wp rsl-ie job wait 73
On our test site with WP-Cron off, it finished the stuck job:
Job 73: processing, 3800 of 5000
Job 73: processing, 5000 of 5000
status: completed
processed: 5000
success: 5000
failed: 0

See WP-CLI for imports and exports for the other commands.
Fix 4: the Continue button (2.1.42 and later)
From version 2.1.42, the Jobs page shows a Continue button (the play icon) next to every import or export that is still running:

Click it, and the job’s progress page opens and runs the remaining batches from your browser, without WP-Cron. On our test site with WP-Cron turned off, an import stuck at 550 of 5,000 rows reached 1,950 within 25 seconds and kept going. Keep the page open until the import completes.
No duplicates after a pause
A stuck import continues from the row after the last finished batch. After both tests, the site had exactly 5,000 imported posts with 5,000 different slugs.
If you’d rather start the same file again from the beginning, set Check for Existing Items by Field to a unique field such as Slug, and If Match Found to Update:

Rows that were already imported are updated instead of created twice. See updating posts without duplicates.
Prevent it next time
- For a large file, keep the progress page open until the import completes. It is the fastest way, and it doesn’t depend on WP-Cron.
- If you leave, check the Jobs page later. If the count hasn’t moved, use one of the fixes above.
- On a site with
DISABLE_WP_CRON, make sure the server cron job exists before you start long imports or schedules.
Before you import
A large import changes thousands of posts at once. Back up the site first, and try the first 20 rows of the file before importing the rest.
With an AI agent
An AI agent connected through the WordPress MCP Adapter (see connecting Claude Code to WordPress) can check on a job you started earlier:
Is the import job 2873 still running? How far has it got?
In our run, on a test site with WP-Cron off, the agent called rsl-ie/job-get. It reported status processing, 550 of 5,000 rows imported, 0 failed, and that the job could be paused or cancelled. The agent can check status and errors, but it can’t make WP-Cron run; for that, use one of the three fixes above.
FAQ
Can I close the tab during an import?
Yes. The import continues in the background with WP-Cron, as long as WP-Cron runs: someone visits the site, or the server runs cron.
Why did my import stop at the same percentage?
The browser tab was closed and WP-Cron didn’t run, either because nobody visited the site or because DISABLE_WP_CRON is set without a server cron job.
Is there a button to continue a stuck import?
Yes, from version 2.1.42: Continue in the Jobs page opens the progress page and finishes the job from your browser.
Will the stuck import create duplicates when it continues?
No. It continues from the next row. In our test, 5,000 rows gave exactly 5,000 posts.
How do I find the job ID?
It’s in the ID column of the Jobs page, and in the job name, for example “#73 Import Blog Posts”.
Do rows with errors stop the import?
No. They are counted as failed and listed in the job details, and the import moves on.
Is a larger batch size faster?
A batch stops after about 20 seconds and the next one picks up where it ended, so a larger batch size is safe. It doesn’t help a job that is waiting for WP-Cron.
Related Guides
- Scheduled Imports Not Running in WordPress? WP-Cron Explained and Fixed
- Import and Export WordPress Content with WP-CLI
- Export a Large WordPress Site Without Timeouts
- Bulk Update WordPress Posts from CSV Without Duplicates
Get the free plugin on WordPress.org.

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