Scans can be interrupted by timeouts, errors, or server issues. Content Guard Pro saves progress automatically, allowing you to resume without starting over.
Why Scans Get Interrupted #
Common causes of scan interruption:
Server Timeouts #
- PHP execution time limit: Default 30-60 seconds
- HTTP timeout: Connection closed by server
- Hosting limits: Some hosts limit background processes
Resource Limits #
- Memory exhaustion: PHP runs out of allocated memory
- Database connection: Too many queries or connections
User Actions #
- Browser closed: Page navigated away during scan
- Manual pause: User clicked Pause button
- Manual cancel: User stopped the scan (not resumable)
Automatic Recovery #
Content Guard Pro handles most interruptions automatically:
Progress Checkpoints #
- Progress saved after each batch
- Current position stored in database
- Finding data preserved
Background Recovery #
1. Interrupted scan detected on next page load
2. Action Scheduler queues continuation
3. Scan resumes from last checkpoint
4. No duplicate scanning of completed items
Manual Resume #
If automatic recovery doesn’t activate:
1. Go to Content Guard Pro → Scans
2. Look for “Interrupted scan detected” notice
3. Click Resume Scan to continue
4. Or click Discard to abandon and start fresh
Resume Information #
The resume notice shows:
- When the scan was interrupted
- How much was completed
- Items remaining
- Option to resume or discard
Checking Scan Status #
Active Scan Status #
At Content Guard Pro → Scans, check:
| Status | Meaning |
| ——– | ——— |
| Running | Scan actively processing |
| Paused | Manually paused, ready to resume |
| Interrupted | Stopped unexpectedly, can resume |
| Completed | Finished successfully |
| Failed | Error occurred, check diagnostics |
Action Scheduler #
For detailed background task status:
1. Go to Tools → Scheduled Actions
2. Filter by “content_guard_pro”
3. Check pending, running, and failed actions
Preventing Interruptions #
Optimize Server Configuration #
// In wp-config.php (if allowed by host)
define('WP_MEMORY_LIMIT', '256M');
Use Safe Mode #
Enable Safe Mode for resource-constrained environments:
1. Go to Content Guard Pro → Settings
2. Set Safe Mode to “Always On”
3. Save changes
Safe Mode uses:
- Smaller batch sizes (25 items)
- Longer delays between batches (5-10 seconds)
- More frequent progress saves
Schedule Strategically #
- Run during low-traffic periods
- Avoid peak database usage times
- Consider your hosting plan’s limits
When to Start Fresh #
Restart instead of resuming when:
Pattern Updates #
If detection patterns updated since the scan started, restart to use new patterns.
Significant Content Changes #
If content was added, deleted, or bulk-edited, a fresh scan is more accurate.
Very Old Paused Scan #
Scans paused for more than 24 hours should be restarted for current results.
Corruption Suspected #
If scan data appears corrupted or findings seem incorrect.
Discarding an Interrupted Scan #
To abandon an interrupted scan:
1. Go to Content Guard Pro → Scans
2. Click Discard Interrupted Scan
3. Confirm the action
4. Start a new scan if needed
Note: Findings already detected are kept in the database. Only the scan progress state is cleared.
Troubleshooting Resume Issues #
Scan Won’t Resume #
1. Check Content Guard Pro → Diagnostics for errors
2. Verify Action Scheduler is working
3. Check available disk space for database
4. Review PHP error logs
Scan Keeps Interrupting #
1. Enable Safe Mode
2. Reduce batch size to minimum (10)
3. Increase batch delay
4. Contact your hosting provider about resource limits
5. Consider upgrading hosting if consistent
Lost Progress #
If progress was lost:
1. Check database for content_guard_pro_scans table
2. Verify no database corruption
3. Start a fresh scan
