This means that your server is stopping the import process before it can complete. WP All Import processes records piece by piece to help prevent this from happening.
Sometimes you can prevent your server from terminating the import simply by lowering the records per iteration. Other times the reason for the termination has nothing to do with the records per iteration.
No matter the cause, the troubleshooting process always starts the same:
Lower the records per iteration. You can control how many records are processed in each iteration in Import Settings ▸ Advanced Options ▸ Iterative, Piece-by-Piece Processing. If your import is still being terminated with 1 record per iteration, then you’ll need to modify your server settings so it will allow WP All Import to run.
Contact your host and have them check your server’s error log. They will be able to see exactly why your server is terminating the import and they will know exactly how to fix it. There isn’t anything we can do to help until your host has checked the error log and we know exactly what the issue is.
Servers have a number of settings that place hard limits on how long processes are allowed to run before they are terminated.
There are the two very common hard limits that our users run in to:
Maximum Execution Time (PHP): This is set in php.ini with max_execution_time. It determines how long a process is allowed to run before it’s terminated. You can ask your host to increase the limit, but this should be considered a last resort.
FCGID Timeouts (Apache): This is set in httpd.conf with FcgidIOTimeout.It determines how long mod_fcgid will wait while trying to perform a read or write. It should be set as high as your host will allow. In our experience 90 seconds is sufficient.
For a list of hosts that work great with WP All Import, see our recommended hosts page.