Outcome
Large exports/imports run in smaller chunks so long-running operations are easier to monitor and less likely to hit memory/time limits.
Batch Large Sites and Multisite Jobs
Avoid timeouts by chunking large media, content, and multisite sync operations.
Video walkthrough
▶
Video walkthrough coming soon.
The YouTube embed will appear here.Risk level
High. Large operations have higher blast radius. Use dry runs, smaller chunks, and monitoring.
Before you start
- Know which integrations are heavy: media, pages, posts, templates, multi-remote groups.
- Set batch size and delay conservatively for shared hosting.
- Use network batch screens when coordinating multisite jobs.
Steps
- Start with a narrow dry run
Estimate item counts and likely duration. - Enable batch processing
Use batch options for heavy workflow steps. - Tune batch size
Smaller chunks are slower but safer on constrained hosts. - Monitor jobs
Use Activity / batch jobs screens for status, failures, and retries. - Clean up old jobs
Use cleanup tools after the recovery window passes.
Screenshots
Engine behavior
The sync engine chunks export items and exposes hooks for batch size and delay while admin screens track network batch jobs, schedules, settings, and activity.
$pathstringRequired
Absolute path of the directory to write the snapshot to.
$modestringOptionaldefault:
two-waySync direction — push, pull or two-way.
$gitboolOptionaldefault:
falseWhen true, commits the snapshot to the repository after writing.
Use batches before you need them
If a full import times out once, switch to batching before retrying. Repeating the same oversized run usually wastes the recovery window.