Our NabWP Automation area helps you schedule recurring care tasks for the selected WordPress website. The available tasks can include website backups, database cleanup, WordPress integrity checks, malware scans and speed tests. Availability depends on the services and permissions enabled for the site, and automatic software updates have their own settings in the Updates area.
IN THIS ARTICLE
01 Configure and check the recurring schedule
Open Automation and review each task separately. Choose the frequency and time offered by the interface, then confirm that the task is enabled. Use the displayed timezone and next-run information when planning a quiet period. A schedule is an instruction for future work, so check the history after the first run to confirm that the operation actually succeeded.
Choose a schedule that matches your website's activity. Backups should reflect how often valuable data changes. Integrity and malware checks help identify issues that may need attention, while a periodic speed test can reveal a trend worth investigating. A task that reports a finding may still require you or our team to act on it.
02 Review cleanup, retention and failed runs
Database cleanup deserves careful review because it can remove items such as old revisions, binned content, spam comments and expired temporary data. Keep a backup and understand what the task removes before enabling it. Do not expect unlimited revision history if a cleanup policy is configured to prune it.
Review backup retention settings for the automated backups the task creates, along with available storage. Also inspect failed or skipped runs instead of assuming the schedule guarantees completion. Our AI tools can suggest a maintenance plan, but you should review the selected tasks and timing. If an automation repeatedly fails, share its reported result and website with our team so the underlying issue can be investigated.
How do I verify a new WordPress maintenance schedule?
- Choose the task and frequency in Automation, using the displayed timezone and next-run information.
- Review cleanup scope and retention before enabling a task that removes revisions, binned content or other stored items.
- Inspect the first completed result and address repeated failures or findings that need action.
Scheduling tells the system when work should be attempted; it does not prove completion. Keep an appropriate backup before database cleanup, and review available storage for retained backups. Automatic software updates have their own settings and should not be assumed to follow a maintenance task's schedule.