Why do scheduled backups get canceled while manual builds complete without any trouble? Low site traffic often keeps WordPress from triggering the build, and a few adjustments to your schedule and build settings resolve the failures for good.

This guide covers resolving scheduled backup build failures in Duplicator Pro, so your automated backups complete every time.

Why do scheduled backups get canceled yet manual builds work fine?

WordPress does not run active background threads. Scheduled tasks, including Duplicator Pro builds, depend on visitor traffic to trigger execution. When site traffic drops too low at the scheduled time, the build may not start or complete properly.

The basic workflow looks like this:

1. A visitor accesses the site.
2. WordPress identifies that a scheduled build needs to run.
3. The backup build process begins.

When traffic is inconsistent, scheduled builds fail or get canceled before completion.

Solutions for Scheduled Build Failures

Adjusting Client-Side Kickoff

In some cases, the Client-side Kickoff setting slows down a scheduled build or causes it to time out. Check and adjust the setting with these steps.

1. Navigate to Duplicator Pro » Settings » Backups, then scroll to the Server Detection section.
2. Find Client-side Kickoff. Duplicator Pro sets this to Auto by default, which lets Duplicator determine automatically whether kickoff is needed based on the loopback detection result. Keep it set to Auto unless a build continues to fail.
3. If scheduled builds keep failing, set Client-side Kickoff to Disabled and click Save & Test Server Detection.
4. Observe the next scheduled backup build.
5. If the scheduled backup builds successfully, the issue is resolved.
6. If the scheduled backup still gets stuck or fails, set Client-side Kickoff back to Auto and proceed to the next solution.

Setting Up a Remote Cron Schedule

A remote cron job ensures consistent execution of scheduled builds, especially on low-traffic sites. To set up a remote cron schedule, refer to the guide How to Make My Scheduled Build Run on Time.

Optimizing Build Settings for Low-Traffic Periods

If traffic is too light when the schedule triggers, builds can time out. Adjust the following settings.

1. Navigate to Duplicator Pro » Settings » Backups, then scroll to the Processing section.
2. Set Server Throttle to Off or Low to speed up builds during peak traffic. Medium and High are also available if your host needs a heavier throttle to avoid resource complaints.
3. Increase Max Build Time to at least 270 minutes, so Duplicator does not auto-cancel the backup before it finishes.
4. Adjust your scheduled build time to coincide with peak traffic periods.
5. If builds must run during low-traffic periods, keep Server Throttle set to Low, Medium, or High to prevent performance issues.

Note: If builds still time out after raising Max Build Time, ask your host to increase PHP’s max_execution_time as well.
Switching Archive Engine to DupArchive, under Duplicator Pro » Settings » Backups » Archive, also helps since DupArchive is fully multi-threaded and more reliable than ZipArchive for large scheduled builds.

Resolving Conflicts with Multiple Scheduled Builds

If multiple Duplicator Pro schedules run on the same server, PHP processes can interfere with each other and cause build failures. Some web hosts limit concurrent PHP processes, which creates conflicts when multiple sites attempt to build backups simultaneously.

To resolve this issue:

• Adjust the schedule times so each site builds at a different interval.
• For example, if multiple sites are set to build at 1:00 AM, stagger the schedules by a few hours.
• Monitor build performance and adjust timings as necessary.

These adjustments to Client-side Kickoff, Server Throttle, Max Build Time, and your schedule timing minimize build cancellations, so Duplicator Pro completes your scheduled backups successfully going forward.