The 'already revalidated' replies come from the CMS data-lag window (a provider completes their revalidation but CMS's public Due Date List still shows them overdue for weeks). Running the refresh 3x/week instead of weekly shrinks that window from up to 7 days to ~2-3, so a provider who just completed stops being targeted faster. No change to the overdue window or audience size -- this is the lever that reduces stale-data complaints without losing prospects. |
||
|---|---|---|
| .. | ||
| ansible | ||
| cron | ||
| fail2ban | ||
| firewall | ||
| mta-sts | ||
| nginx | ||
| postfix | ||
| systemd | ||