fix(integrations): Handle forbidden errors in integration proxy#111123
Merged
fix(integrations): Handle forbidden errors in integration proxy#111123
Conversation
Add explicit handling for ApiForbiddenError exceptions in the integration proxy endpoint, with a dedicated failure metric type and logging. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> Agent transcript: https://claudescope.sentry.dev/share/oNzq7eK2wMWD7OoHr5s1_AD3gu1MmOD6sXtqsRX5sTM
github-actions
bot
added
the
Scope: Backend
trevor-e
approved these changes
Mar 19, 2026
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.
Add explicit handling for
ApiForbiddenErrorin the integration proxy endpoint'shandle_exception_with_detailsmethod, following the same pattern established in#111030 for
ApiUnauthorizedandApiRateLimitedError.Previously,
ApiForbiddenErrorexceptions fell through to the unknown error handler,which logs at warning level and delegates to the base class (returning 500). Now it
returns the correct 403 status with a dedicated
forbidden_errorfailure metric typeand info-level logging.
Agent transcript: https://claudescope.sentry.dev/share/IV3nYCdnIAW35SRn4N0wnSGyQrw4sP8303Ea3PzRkjE