Leads: schedule the campaign tick (pg_cron) - #125
Merged
Merged
Conversation
The campaign machinery existed but nothing drove it — campaigns only moved when someone clicked "Run now", which makes it manual outreach with extra steps. This is the pg_cron job that closes the loop. Every 15 minutes, matching scan-watches. The tick is cheap and usually idle: it selects only active campaigns and each is bounded per tick (15 discovered, 8 researched, 5 sends). Faster would not help, because the slow step is the scan worker and the daily caps are the real throttle. A tick will not send from a campaign with auto_send off, which is the default. Those discover, scan, research and draft, logging every message as a dry run — turning sending on stays a separate deliberate act, still gated on a CAN-SPAM postal address. Applied to production; verified scheduled and active. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the
pg_cronjob that drives outreach campaigns. Without it the machinery existed but only moved when someone clicked Run now.crawlproof-outreach,*/15 * * * *, same pattern ascrawlproof-scan-watches(readssite_url/cron_secretfrompublic.cron_config)auto_sendoff (the default) — those discover, scan, research and draft, logging every message as a dry runApplied to production and verified
active = true. There are currently 0 campaigns, so the tick is a no-op until one is created.🤖 Generated with Claude Code