Trace view doesn't scroll to the selected span when opening large traces (Explore → Traces)

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. In Explore → Traces, run a query that returns span results.
2. Click a span in the results that belongs to a large frontend trace (thousands of spans).
3. Observe where the trace view lands.
4. 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

Start in Explore → Traces and trace the Explore/EAP trace endpoint through the trace-view scroll-to-span behavior. Check how the view handles a selected span that is outside the bounded set loaded for a large trace. Done means selecting such a span opens the trace at and highlights the requested span, while existing small-trace behavior remains intact.