You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a span is still open after TRACES_CLEANUP_INTERVAL (5 min), the
cleanup timeout now marks it with SpanStatus ERROR / deadline_exceeded
and sets `trace.timed_out = true` before calling end(). The
`excludeEvents` beforeSendTransaction hook drops any event carrying that
flag, so artificially-clamped spans (p50 ≈ 300,014 ms for
"Onboarding - Overall Journey") are never sent to Sentry. Legitimate
long-but-real spans are unaffected because the drop is keyed strictly
on the flag, not on duration.
Co-authored-by: Cursor <cursoragent@cursor.com>
0 commit comments