Unresolved/Archive issue status not filtering events on Explore -> Errors page.
Author: rodolfoBeeCreated Sep 16, 2026Updated Sep 17, 2026
LabelsProduct Area: IssuesBug
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
- Go to Explore -> Errors
- Use the
is:unresolvedquery
Expected Result
Only events from unresolved issues are returned.
Actual Result
The filter has no effect on the page. See screenshots:
Issues in the project: this project has one archived, one resolved, and one unresolved issue.
Searching for is:unresolved returns all issues (same behaviour for is not: resolved
Additionally, is:archived returns no issues:
And is:resolved returns the correct result:
Using is:ongoing is not an option:
Invalid value for "is" search, valid values are ['archived', 'ignored', 'muted', 'reprocessing', 'resolved', 'unresolved']
This search also affects the filters used in alerts, causing alerts to trigger/not trigger incorrectly.
Related to https://github.com/getsentry/sentry/issues/122790
Reported in an internal ticket via support
Product Area
Explore
Link
DSN
No response
Version
No response
Source: getsentry/sentry