new-site/infra/cron/pw-hc-campaign
justin 9fa2c86f01 fix(warmup): HC cron logged to /var/log (deploy can't write) -> cron silently died
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.
2026-06-09 16:06:28 -05:00

13 lines
1.1 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 warmup: import the next slice across ALL active segments
# (revalidation, OIG screening, NPPES, reactivation, bundle) into listmonk-hc
# and keep each campaign running. Mon-Fri only, 7 AM Central (host TZ =
# America/Chicago). Delivery is throttled by pw-hc-rampcap's sliding-window
# cap, sent ONLY via the hc HOT stream (.107-.109). Segment audiences are
# source-grounded: a segment with no matching providers simply imports nobody.
# Deliverability guard: warmup only mails SLIGHTLY-overdue providers (1-90 days
# by default, HC_OVERDUE_MIN/MAX) -- recently-lapsed practices still have live
# inboxes; heavily-overdue ones likely bounce and burn the warming IPs.
0 7 * * 1-5 deploy cd /opt/performancewest && HC_VERIFIED_CSV=/opt/performancewest/data/hc_warmup_nongoogle.csv python3 scripts/build_healthcare_campaigns_cron.py --start-campaign >> /opt/performancewest/logs/pw-hc-campaign.log 2>&1