Error Grouping
Automatic fingerprinting and grouping of identical errors with frequency tracking, frequency buckets based on event counts, and status management.
Error grouping automatically combines identical errors into single groups — instead of seeing 1,000 individual errors for the same bug, you see one error with a count of 1,000. This reduces noise and helps you focus on unique issues.
Identical errors grouped together
See occurrence count and trends
No configuration needed
How errors are grouped#
Errors with the same message, stack trace and platform are grouped into one issue. Any difference in the message or stack trace text starts a new issue.
When Errors Are Grouped#
- Same error in different user sessions
- Repeated error from same user
- Same error across environments and releases (if same platform)
- Different error messages
- Different stack traces (even a changed line number)
- Different platforms (flutter_web vs flutter_android)
Understanding Error Groups#
Each group tracks:
1,247
Occurrences
2025-11-10
First Seen
2025-11-12
Last Seen
Open
Status
Frequency Buckets#
Each group is placed in a frequency bucket based on its event count (the Issues page's Frequency filter; the API calls this severity):
| Frequency | Events | Color |
|---|---|---|
| Very frequent | > 100 | |
| Frequent | 51 - 100 | |
| Recurring | 11 - 50 | |
| Rare | 1 - 10 |
Managing Error Groups#
- Status Management: Open, In Progress, Resolved, Archived, Ignored
- Bulk Operations: Select several groups to change their status or delete them
- Filtering: Filter groups by status, frequency, time range, platform, environment, release, or search text
Best Practices#
Groups with 51+ events usually impact the most users
Keep error statuses updated for team coordination
Track when errors appear and whether they recur after fixes (resolved groups are not reopened automatically)
Correlate error groups with specific deployments
Archive issues you no longer expect to see to keep the dashboard clean