From b09fc3355f07ed25e475ec387a8ce960cd39a1d5 Mon Sep 17 00:00:00 2001 From: Neel Shah Date: Tue, 21 Oct 2025 15:05:36 +0200 Subject: [PATCH] feat(develop): Add note about stacktrace frames truncation --- develop-docs/sdk/data-model/event-payloads/stacktrace.mdx | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx b/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx index 7990c3b5b77b6..f3b5132a22637 100644 --- a/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx +++ b/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx @@ -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