Pause scheduled ETL runs - #111
Merged
Merged
Conversation
Signed-off-by: capituwuistgoonsquad <ultimamaster13@gmail.com>
Signed-off-by: capituwuistgoonsquad <ultimamaster13@gmail.com>
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
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.
Summary
Safety
Validation
Post-merge run
Use blank state LittleSis fields, enable the reviewed House, Senate, and Congress.gov modes, and keep GovTrack profile enrichment disabled. Do not overlap runs; keep full runs at least one hour apart and ordinarily to no more than three per UTC day while OpenStates is active. Monitor the run at 30-minute intervals and inspect ETL_SUMMARY_JSON for local caps, upstream quota observations, breakers, and write reconciliation.
Greptile Summary
This change pauses scheduled ETL execution and keeps the scraper available through an explicitly configured manual run. Manual write modes remain disabled by default, runs remain serialized and time-bounded, and successful scraper runs still trigger the frontend deployment.
Confidence Score: 5/5
Safe to merge: the manual workflow and deployment handoff behave as intended.
No blocking failure remains.
What T-Rex did
Reviews (2): Last reviewed commit: "Update Senate policy contract for manual..." | Re-trigger Greptile