Unrelated errors are grouped together

[aludvigsen]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

9.x

Framework Version

Next 15.3.2, TRPC 11.1

Link to Sentry event

No response

Reproduction Example/SDK Setup

I upgraded from version 7 to version 9, and after the upgrade a lot of my errors are grouped together even though they are not related except they all are "TRPCError"s.

Steps to Reproduce

Triggering an error in different trpc procedures.

Expected Result

Triggering an error from different procedures should result in a separate issue per error.

Actual Result

Errors ends up in the same issue on Sentry with the title and message from the initial error shown on top.

[andreiborza]

Hi @aludvigsen, thanks for filing this. We briefly discussed this on discord where I suggested trying to downgrade to 9.19.0 (version before we added isolation scope forking for the tRPC middleware) but that did not alleviate the issue.

in v9.19 it differentiates queries and mutations, but different mutation endpoints (trpc-endpoints) still get merged together.

[chargome]

Hey @aludvigsen would you mind pasting a link to two of these events that should not be grouped together? 🙏

[aludvigsen]

Here is an example with two sample events.