The Pro weekly digest reminds staff about stored passwords marked ageing or breached. It uses saved information; it does not perform a fresh breach check or change passwords.

Check the settings and jobs

1. Confirm Pro is active.
2. Review Flag vault passwords older than (days) in module Settings.
3. Review the relevant entries and saved breach results in Health.
4. Open the PD Modules jobs view and locate Weekly password-health digest.
5. Check its enabled state, most recent run time and summary alongside the platform cron status.

The job is checked daily, but its digest is due on Mondays according to the installation’s time. It is not a promise of an email at a particular hour. A run on another day can correctly report that it is not due.

Interpret the summary

The digest counts ageing passwords and saved positive breach flags. It does not include every weakness or repeat detected by Health, and it does not send individual entry secrets. Check the staff recipients and platform mail delivery evidence if an expected digest is missing.

A “reported” count is not proof that an email reached an inbox. With no recipients, a run can still mark that date processed; repeatedly running it on the same day is not a guaranteed resend. Diagnose the run and delivery evidence first.

Keep expiry cleanup separate

One-time secret sweep is a separate job. Do not disable it as a way to silence the weekly digest. An expired link is denied by retrieval checks, while cleanup of stored expired values depends on the sweep running. Compare the job’s last run time and summary with the cron status before requesting another run.

See the PD Password Manager WHMCS guide for related tasks, or explore PD Password Manager.