9fa2c86f01
The HC warmup builder ran from cron at 07:00 but the >> /var/log/pw-hc-campaign.log redirect failed (deploy user cannot write /var/log), and a failed output redirect makes cron abort the command BEFORE it runs -> HC sent 0/day since the log file was removed. Route HC cron logs to /opt/performancewest/logs/ (deploy-owned) so the redirect always succeeds. Builder itself was fine (verified: imports + sends work, 0 bounces). Also removed the stale 'campaign-warmup.sh 122' root-cron line that pointed at a finished campaign + no longer existed.
13 lines
1.2 KiB
Text
13 lines
1.2 KiB
Text
# NOTE: logs go to /opt/performancewest/logs/ (deploy-owned). The deploy user
|
|
# cannot write /var/log, so a /var/log redirect makes cron silently fail before
|
|
# the command runs. Ensure /opt/performancewest/logs exists + is deploy-owned.
|
|
# Healthcare data refresh: re-check every emailable NPI against the live
|
|
# government sources (CMS Revalidation list, OIG LEIE) + MX re-classification
|
|
# (Google-host detection) so warmup sends never go stale. Runs Mon/Wed/Fri 06:00
|
|
# Central, ~1h before the 07:00 weekday send. Mon/Wed/Fri (vs weekly) shrinks the
|
|
# CMS data-lag window to ~2-3 days, so a provider who just completed their
|
|
# revalidation stops being targeted faster (fewer "already done" replies).
|
|
# Takes ~8 min. SAM is opt-in (--sam-pages); SAM exclusions rarely carry an NPI,
|
|
# so OIG LEIE is the NPI-bearing exclusion source. Then prune-only removes newly-
|
|
# Google-hosted and suppressed subscribers from the warmup lists.
|
|
0 6 * * 1,3,5 deploy cd /opt/performancewest && python3 -u scripts/hc_data_refresh.py >> /opt/performancewest/logs/pw-hc-refresh.log 2>&1 && python3 -u scripts/build_healthcare_campaigns_cron.py --prune-only >> /opt/performancewest/logs/pw-hc-refresh.log 2>&1
|