Bug in the TraceView. probably regression Exceptions started to be shown out of their group and order.

[amiranvarov]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Would be hard to give me instructions how to reproduce. You should set up microservice architecture app.

I think it would be easier if I share my screen with parts of my code with you as i can't expose my private repo itself.

before you tell me to look at my code search for issues there, i'll tell you I did it for the past 5 hours, i have been going trough my code to see if i broke something. i reverted back to commit when my sentry Trace view was perfectly showing me in the timeline where exactly exception was captured, in which of my microservice, after which span and etc. But even after i checked out that commit when sentry and my code was aligned perfectly, i'm still having an issue with how TraceView is displaying exceptions positon on my trace timeline. I am very confident that problem is not in my code.

Out of nowhere, Sentry right now is showing captured exceptions out of order and not correctly. I suspect maybe there was some issue with latest realese of traceview, on Sentry side.

Expected Result

Exceptions are being displayed in the order, in related group, just like it was a weegkago

Actual Result

Exceptions started to be displayed out of order, out of the group

Product Area

Performance

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-performance for triage ⏲️

[k-fish]

@amiranvarov hey we'll take a look, but in the meantime can you possibly give us the projectId or your organization slug so we can look at this trace in particular?