Batched scanning limits the work done in one sweep. The interval and batch size determine how frequently a particular domain is revisited; a daily job does not mean every domain is checked every day.

Configure the sweep

1. Open PD Modules → Domain Radar → Settings.
2. Review Sweep the portfolio automatically.
3. Set Domains to check per sweep within the displayed range, considering portfolio size and registry response times.
4. Review Keep checking domains after they expire. With this off, domains expired more than 30 days ago are skipped from the checking batch.
5. Save and check normal Blesta cron operation and the module’s latest sweep result.

The scheduled job is registered daily and needs an active module licence. Scan now is a separate manual batch and does not depend on the automatic-sweep switch. It also suppresses the digest for that manual run.

Review actual progress

Never-checked rows come first, followed by oldest checked rows. A large or growing portfolio can therefore take several sweeps to revisit. Each registry request has a timeout, but the whole batch is sequential work and can take substantially longer than a single request.

Platform synchronisation is also bounded. On Blesta, the candidate limit is applied to services before domain recognition, so a large service book can reduce domain coverage. The portfolio display and search also use a limited set.

If coverage appears incomplete, record the watched count, batch size, checked times and expected domain states. Check synchronisation coverage separately; raising the batch size does not change an earlier synchronisation limit.

See the PD Domain Radar Blesta guide for related tasks, or explore PD Domain Radar.