Issue
When an error event shows a Related Exceptions section (linked errors via cause), the issue title uses the cause error instead of the outer error. Different wrapper errors that share the same cause can look identical on the Issues list.
Applies To
All SaaS Customers and Self-Hosted Users
Issues
JavaScript SDK
Symptoms
You wrap a cause such as
AxiosErrorin a more specific error (for exampleRoute not found), and the issue title showsAxiosErrorinstead of the wrapper.Different product failures that share the same underlying cause group or title as if they were the same problem.
Resolution
This bug is fixed. Upgrade the JavaScript SDK to version 7.104.0 or later.
Check your installed
@sentry/*package version.If the version is at least
7.46and below7.104.0, upgrade to7.104.0or later.Deploy the upgrade, then confirm new events use the outer error for the issue title and grouping.
Affected versions incorrectly marked linked errors as exception groups. Sentry then picked the wrong main_exception_id, so the cause drove the title and grouping instead of the outer error. Background is in the linked exceptions GitHub issue and this engineering explanation. The fix landed in JavaScript SDK 7.104.0.
If you already use 7.104.0 or later and the title still does not match the exception on the event you are viewing, that is a different case. See Why doesn’t the issue title match the exception?.
For how linked cause chains appear in Sentry, see the LinkedErrors integration docs.