Errors disappearing into the void?

I'm uploading errors from a Node.js application using Raygun4Node. They're being submitted, and getting a "202 Accepted" response code, but only certain types of errors are getting through, and I can't see why.

Some errors are coming through fine, such as "The specified mark as off category is invalid.", but I'm also expecting some "The specified event type is invalid or disabled." errors, and they seem to be disappearing somewhere.

Is it possible for messages to fail processing after returning 202 Accepted? If so, can I see those failures somewhere?

---

Hi Lee,

Are you able to capture one of these exceptions as it's being sent to Raygun? It's unlikely since it's our provider, but sometimes we do get malformed error messages come through, and they get discarded. Alternatively if you could give me a date and time (preferably in UTC) you sent one of these exceptions it'll make digging through the error reports easier.

Thanks, Jamie

---

Hi Jamie,

I did capture it, and I thought it looked fine, but I probably should have inspected it more closely... I think a module I'm using to capture longer stack traces might be causing Raygun4Node to send incorrect data for the StackTrace part of the payload.

I'll look into it further.

---

OK, it looks like the errors actually did come through just fine, but every single error that's raised by the Tedious module is being considered part of an existing error group. Is there anywhere I can see how errors are automatically grouped?

---

Here's the two errors, if that helps - I would have thought they'd be different enough to be counted as separate errors.

---