Aggregated exceptions search not working.

[rodolfoBee]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

1. Send a aggregated exception such as:

2. Try to search for InternalServerError on the issues page
3. Try to search for ReplyError on the issues page

Expected Result

The events/issues are found for both 2 and 3.

Actual Result

No event is found when searching for InternalServerError, only ReplyError gives results.

The current workaround is to search using error.type:InternalServerError.

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

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

[ceorourke]

Hi @rodolfoBee how do you send an aggregated exception?

[johanholmerin]

Original reporter here. I encountered this in a Node.js project where we add additional information to errors by wrapping them using Error#cause.

} catch (error) {
  throw new InternalServerError('Unknown error', { cause: error });
}

We send the aggregated error to Sentry using captureException(error) and both the errors show up in the same issue in Sentry, it's just not possible to search for InternalServerError.