Un-catched errors grouped as one error in sentry

Sentry is weirdly grouping all un-catched errors as a single error, even when their stack trace is completely different.

For example,
Exception inside application: GameMembers matching query does not exist

Exception inside application: must be str, not NoneType

are grouped as single error? Why is it happening so? Let me know if you need any details.

I am running Sentry version 10.1.0

Hey, since you’re mentioning that the two errors have two completely different stacktraces it would be great to see the stacktraces to know what you mean. If there’s a stacktrace we generally do not do much with the error message in terms of grouping.