Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- In Explore → Traces, run a query that returns span results.
- Click a span in the results that belongs to a large frontend trace (thousands of spans).
- Observe where the trace view lands.
- For comparison, repeat with a span that belongs to a small trace.
Expected Result
Opening the span scrolls to and highlights that span in the trace waterfall, the same behavior seen with smaller traces.
Actual Result
For the large trace, the parent trace opens but the view does not scroll to or highlight the selected span; it lands at the top of the trace with no indication of where the span is, and no error is shown. For a small trace, the same action scrolls to the span correctly. We can reproduce both cases, one trace where it works and one where it does not (specific links in the linked internal ticket).
Notes from investigation:
- The Explore/EAP trace endpoint loads a bounded set of spans per trace; spans beyond that set are not loaded into the view.
- When the selected span is not in the loaded set, the scroll-to-span step exits silently (logged internally, no user-facing message).
Product Area
Explore
Link
No response
DSN
No response
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Expected Result
Opening the span scrolls to and highlights that span in the trace waterfall, the same behavior seen with smaller traces.
Actual Result
For the large trace, the parent trace opens but the view does not scroll to or highlight the selected span; it lands at the top of the trace with no indication of where the span is, and no error is shown. For a small trace, the same action scrolls to the span correctly. We can reproduce both cases, one trace where it works and one where it does not (specific links in the linked internal ticket).
Notes from investigation:
Product Area
Explore
Link
No response
DSN
No response
Version
No response