Skip to content

Clarify behaviour for AggregateExceptions in the SetBeforeSend hook #14265

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
+2 −0
Open

Clarify behaviour for AggregateExceptions in the SetBeforeSend hook #14265

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2cf0a26
Clarify behaviour for AggregateExceptions in the SetBeforeSend hook
jamescrosswell Jul 7, 2025
9f6de50
Update docs/platforms/dotnet/common/configuration/options.mdx
jamescrosswell Jul 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/platforms/dotnet/common/configuration/options.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -225,6 +225,8 @@ This function is called with an SDK-specific message or error event object, and

By the time <PlatformIdentifier name="set-before-send" /> is executed, all scope data has already been applied to the event. Further modification of the scope won't have any effect.

When filtering based on exception types, the original exception (including any `AggregateException`) will be stored in `SentryEvent.Exception`. However, Sentry's `MainExceptionProcessor` unpacks AggregateExceptions automatically, and so what you will see in Sentry will be the various inner exceptions. These are also available in the SDK by inspecting the `SentryEvent.SentryExceptions` collection.

</ConfigKey>

<ConfigKey name="set-before-breadcrumb">
Expand Down