Raygun messages get merged into one

We have a case where multiple different error reports with similar error messages are (wrongly) grouped into a single error group. This is a big problem for us because it effectively hides new errors.

Not sure support staff has access to this but here is the URL of one of the cases: https://app.raygun.io/crashreporting/ffrb4a/errors/939691501#6256994881

---

I'm seeing this as well. It seems to happen in javascript projects (using raygun4js), but not in our .NET projects.

Here's a group containing a number of different errors: https://app.raygun.io/crashreporting/f5iqgk/errors/991187613#latest

---

Hi Guys,

I replied to each of you individually as it was two quite separate issues.

Fabian's issue was resolved by switching the application to using the message based hasher. This is a good solution when you desire to have unique groups for each message instead of relying on our default grouping behavior which mainly groups by elements of the stacktrace.

Bryan's issue relates to JavaScript errors with small/non existent stacktraces being grouped incorrectly and requires a update to our JavaScript error hasher so we can handle these cases better.

We hope to deploy an update to the JavaScript hasher in the near future to fix this issue. This thread will be updated when this has happened and the option is available.

Cheers,
Alex

---

We're trying out Raygun to see if it's the app for us. I've been flummoxed by this exact behavior, as it's totally misleading when you are looking at an old error that's 'hiding' new errors. I'm seeing the counter increment but the new error isn't showing; it's being aggregated into the old error group.

I see that it hasn't been fixed since 01/16. Also, I've integrated Raygun into our Slack and Raygun isn't dispatching error notifications to our channel.

---