Skip to content

feat(develop): Add note about stacktrace frames truncation #15273

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

Merged
merged 1 commit into from
Oct 21, 2025
Merged

feat(develop): Add note about stacktrace frames truncation #15273

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 4 additions & 0 deletions develop-docs/sdk/data-model/event-payloads/stacktrace.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ follow this rule of thumb:
ordered from caller to callee, or oldest to youngest. The last frame is the
one creating the exception.

In cases where the event payload is oversized (for instance, for recursion / stackoverflow errors),
some SDKs truncate the frames to make sure the event gets sent and is not dropped completely.
The recommended way to truncate in this case is take 500 frames on both sides so that Relay can further truncate on both sides as it wishes.

`registers`

: _Optional_. A map of register names and their values. The values should
Expand Down
Loading