Schedule imports

Validate manually first

Complete a manual import and check the public output before enabling a schedule. Resolve held feeds and incorrect mappings before asking a background job to apply them repeatedly.

Choose the schedule and policy

In the event's connection settings, choose the available interval or daily/weekly timing that fits the event. Review the site's configured timezone for scheduled times.

Choose automatic application when a validated scheduled import should update stored data without a review step. Choose a preview policy when a person should review the changes first. Validation still applies to automatic imports.

Arrange reliable execution

WordPress cron depends on site execution. A schedule on a low-traffic site may run late. For predictable unattended operation, ask the host to configure a real cron runner for the correct WordPress installation and user.

The host must process both scheduled imports and the worker events that advance queued jobs. Triggering a job is not proof that it completed.

Verify without visitors

After configuration, leave the site alone and check import history after the expected run. Confirm completion, not just a queued status. xCloud testing demonstrated an unattended import, but other hosts need their own acceptance test.

Avoid overlapping work

Do not launch multiple cron systems or repeated manual jobs to compensate for a paused worker. Check the existing job, server cron and licensing/network access first.

For hosting administrators, see WP-CLI operations. For failures, see Troubleshooting.