Fix missing Sentry stacktraces on error events#122
Merged
timothedelion merged 1 commit intomainfrom Mar 20, 2026
Merged
Conversation
When a 401 token refresh fails, the error was logged with logger.error which produces Sentry events without stacktraces. Switching to logger.exception includes the active exception context so Sentry displays a proper stacktrace. Issue: APPAI-515
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
Sentry error events triggered by
logger.error()inside exception handlers were missing stacktraces becauselogger.errordoesn't includeexc_info. This switches tologger.exception()where an active exception context exists.Issue: APPAI-515
Changes
In the HTTP client's 401 token-refresh failure path, replaced
logger.errorwithlogger.exceptionso the activeHTTPStatusErrorexception context is forwarded to Sentry, producing a proper stacktrace in error events.