Fix stalled PRIZM collection and prioritize major-donor coverage - #13
Merged
Merged
Conversation
|
🚅 Deployed to the prizm-api-pr-13 environment in prizm-api
|
railway-app
Bot
temporarily deployed
to
prizm-api / prizm-api-pr-13
September 7, 2026 00:17
Destroyed
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
railway-app
Bot
temporarily deployed
to
prizm-api / prizm-api-pr-13
September 7, 2026 00:18
Destroyed
This branch was successfully deployed
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
2 participants
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.
Daily enrichment repeatedly selected postal codes with missing optional net worth, producing cache hits instead of new captures. Collection now uses a private major-donor cohort and permanent capture history, with an atomic limit of ten new codes per Vancouver calendar day. Salesforce processes the daily selection in individual queueable transactions.
Historical imports add absent postal codes without overwriting current records or inventing fresh capture timestamps. Dashboard, CSV exports and the existing weekly report distinguish new captures, cache hits, failed attempts and cohort coverage. Production startup snapshots the original database and serializes worker migrations.
Validation: 31 Python tests and Ruff pass; Salesforce validation-only deployment passed all six tests. Browser checks covered desktop/mobile dashboard, cohort CSV and report preview. Source databases and donor cohort data are excluded from this PR. Rollout imports historical data and cohort membership before activating the Salesforce changes.