getsentry / getsentry/sentry

Issues not removed from a list when time range is exceeded in real time issues / feed

Open
#113,783 3 comments 0 reactions 0 assignees View on GitHub
Improvement Product Area: Issues
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
21h 10m
Merged PRs (30d)
635

Description

### Environment

Self hosted

### Steps to Reproduce

1) I select projects, env and time range (30min) + only unresolved error or outage and turn on real-time updates (the play button)
2) New issues pop up in the list, that is ok
3) Issues grow > 30min old
4) Issues should therefore disappear, because they do not match the time range anymore
5) Issues persist on the page

### Expected Result

Issue is not shown on the page because it has last seen date is > 30min ago (e.g. 2 hours)
AKA - no bugs anymore 🥳

### Actual Result

Issue is still shown on the page, even if last seen is > 30min ago (e.g. 2 hours)

When doing a full page reload, issue does disappear.

This makes it look like there has been a problem in the last 30 minutes, which it hasn't.

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

26.3.1

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the Issues page with a 30-minute time range and real-time updates enabled. Compare the live-update behavior with a full page reload, then verify that issues whose last-seen time exceeds the selected range disappear without reloading.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.