WordPress missed a scheduled backup: what to check first
Work out whether the job missed its schedule or the report missed its destination. Follow the trail before changing settings.
A missing report is a reason to investigate.
Check the backup plugin’s own history first. If the job ran, investigate reporting and connector delivery. If it did not run, inspect its schedule, WordPress cron and hosting limits. An overdue observation alone cannot establish which of those paths failed.
Check the source
Did the backup plugin record a completed job?
Check the schedule
Was the task due, and did the scheduler execute?
Check delivery
Was the resulting metadata accepted by the monitoring hub?
A heartbeat establishes connector contact. It is not a substitute for a backup completion report.
Establish which deadline you are comparing
Write down the expected interval, grace period and last recorded completion time. Then compare the timestamps in the same timezone. A local-time plugin log and a UTC monitoring report can look inconsistent while describing the same event.
In BackupTool, an expectation is an interval plus a grace period, not a calendar appointment such as every day at 03:00. The first interval starts at site creation; later intervals start from the reported completion time. Keep that distinction in mind before changing a schedule.
With a 24-hour interval and 60-minute grace, a completion reported at 10:00 UTC is expected to be followed by another report within the next 25 hours. This example is not a promise that the backup software will start at a particular clock time.
Look at the backup software first
Open the most recent job log on the monitored WordPress site. A finished job, a running job and no job entry lead to different investigations. Keep the original error text and timestamp before retrying anything.
If a job is still running, do not immediately start another full backup. Check the provider’s recovery or resume instructions. Concurrent jobs can make a limited hosting account harder to diagnose.
- Completed job: compare its finish time with the monitoring record.
- Running or failed job: inspect the provider’s log and its resume guidance.
- No job entry: review the enabled schedule and scheduler execution.
- Transfer error: investigate storage credentials, quota and provider responses.
Check WordPress cron and the hosting scheduler
WordPress cron normally checks due tasks when pages load. On a quiet site, scheduled work may start later than expected. A hosting scheduler can invoke cron independently of visitor traffic, but it still needs a working configuration.
Ask the host for evidence of recent execution and errors. Check that the task calls the correct installation and that a disabled WordPress cron setting has a functioning replacement. Do not disable the existing trigger before confirming the replacement works.
Also inspect Site Health and loopback problems. A firewall, authentication rule or maintenance setup can interfere with requests used to start scheduled work. Follow the host’s instructions rather than copying an unrelated cron command.
- Confirm the correct site path or URL.
- Check when the host’s scheduled task last ran.
- Look for loopback failures and resource-limit errors.
- Compare the job log again after correcting the cause.
If the job ran, inspect connector delivery
A backup can complete while its monitoring event waits for delivery. Check whether the connector is enabled and paired with the right site. Inspect its last accepted contact, pending queue and retained exceptions.
A recent heartbeat with no job report suggests a different question from an entirely silent connector. Review whether the installed backup software and its event are supported by the adapter. Never relabel an old heartbeat as backup success to clear an observation.
After resolving the cause, confirm a genuine new job result reaches the correct workspace. Preserve the original missing-signal record as part of the investigation.
Your next steps
Use these checks as you work. Ticks stay on this page and are not saved as monitoring or recovery evidence.
Where BackupTool fits
BackupTool highlights overdue reporting expectations and shows job evidence separately from connector contact. It helps direct an investigation, but a missing signal does not diagnose the backup plugin or prove that the website is down.
Read the connection guideSources and further reading
Editorial attribution and reading paths updated on 14 October 2026. Prepared against the linked documentation on 11 October 2026. Follow your backup provider’s current instructions for its specific tools.