Ungroup errors?

Raygun grouped the following two errors together:

[FaultException: TranslateApiException: ServerTooBusy : ID=5641.V2_Soap.Translate.3D5852BC]

[FaultException: ArgumentException: The incoming token has expired. Get a new access token from the Authorization Server. : ID=6346.V2_Soap.Translate.267BD484]

How can I ungroup them? One was fixed days ago, the other is going to need a retry around it (or to be ignored, since it will be retried higher up the stack)

For those at Raygun that can access it, here's the actual group: https://app.raygun.io/dashboard/bdd5uo/errors/708534529

I don't understand Raygun's grouping, and it is very frustrating. Sometimes things that differ only by a number don't get grouped together and sometimes things like this which are completely different exceptions DO get grouped together.

---

Raygun contains logic that constructs the identity for an error instance based on its code path, as represented by its stack trace and other unique data (usually the class name). This is done on a per-language basis as the available data and its quality vary across languages.

It looks as though this is a service which in this instance is hitting an edge case in our .NET logic. This normally automates and sanitizes various input e.g web requests from ASP.NET to provide a good experience out-of-the-box for the common cases, but as you've noticed it's impossible to guarantee perfect grouping across all frameworks. Essentially in this case you need some amount of message-based grouping, which we can't do in the base case as most exceptions provide junk instance data in the message which would cause instances to be split out erroneously.

We're going to be working on an alternative approach to the current behaviour which will give much finer-grained control over grouping, so that you'll be able to specify exactly when errors are split or combined into groups yourself. This should be available in the near term and we will update this thread and announce it on the blog when more details are available.

---

Thanks for the response, I look forward to the enhancements.

---

Are there any updates on this? We're also hitting a bunch of errors getting grouped together that actually have nothing ot do with each other. Also .Net related

---