Where did the other 141 reports go?
Nowhere. Every report stays inside the error, in order, with its own backtrace, breadcrumbs, request, user, and tags. You get one problem to triage without throwing away the evidence.
One error, not hundreds of duplicates
Telebugs recognizes reports caused by the same error and keeps them together, so one noisy bug does not fill your list with duplicates. If it gets the grouping wrong, fingerprints and manual merging put you in charge.
How does Telebugs know they belong together?
It looks for stable evidence: a fingerprint from the SDK, useful application frames, the exception type and message, then a safe fallback when an event has little context. Request IDs and other changing values do not need to turn one bug into a hundred errors.
What if the boundary is wrong?
Give future reports a custom fingerprint when your code knows the right boundary. If one bug has already landed in separate errors, merge them in Telebugs and future matches keep going to the final error.
Do my Sentry fingerprints still work?
Yes. Telebugs reads the fingerprint sent by your Sentry SDK,
including an exact {{ default }} component when you
want the usual grouping plus one stable detail from your app.
Will an upgrade reshuffle my history?
No. Grouping improvements look forward. Telebugs does not move old reports or silently rebuild your error list after an upgrade.