fix(ingest_policy): skip 403/HTTP errors per policy instead of crashing#441
Merged
Merged
Conversation
A single inaccessible policy endpoint was aborting the entire ingest run. Wrap raise_for_status() in try/except in all three per-policy fetch functions so failures are logged and skipped, letting the loop continue. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.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
ingest_policy.pycalledres.raise_for_status()unconditionally inside the per-policy loops, so a single 403 (or any HTTP error) on one policy endpoint aborted the entire run and left the workflow inerrorstateraise_for_status()intry/except requests.exceptions.HTTPErrorin all three affected functions:get_all_policy_with_permission,get_all_policy_with_column_permission,get_all_assign_usersTest plan
initial_ingest_policyandincremental_ingest_policytasks no longer error on accounts where the API key lacks access to some policy endpoints🤖 Generated with Claude Code