getsentry / getsentry/sentry

Backend Insights (Laravel) table cursor not reset when filtering

Open
#102,867 4 comments 0 reactions 0 assignees View on GitHub
Bug Product Area: Performance
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

- Have more than 1 page of "paths" (didn't test command/jobs table) and go to the second page
- Click a "Path" and use the "Add to filter"

### Expected Result

Table with paths showing the paths I filtered on.

### Actual Result

Image

Empty table because the `tableCursor` is still present and current filter does not have enough data to have multiple pages. But the "Requests" widget shows there is data. Manually removing the `tableCursor` query param shows the data as expected or use the pagination controls to go back to the first page.

### Product Area

Insights

### Link

https://devalex.sentry.io/insights/backend/?end=2025-10-15T21%3A59%3A59&project=4506659379740672&query=transaction%3A%22%2Fapi%2Fv1%2Fdomains%22&start=2025-09-30T22%3A00%3A00&tableCursor=0%3A10%3A0

### DSN

_No response_

### Version

_No response_

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue in the linked Backend Insights Laravel view by moving to a later paths page and applying an “Add to filter” action. Trace how filtering preserves the tableCursor query parameter; done means the filtered table displays available results without manually removing tableCursor or returning to the first page.

Written by the indexing model from the issue text.

Assessment

Tech stack
laravel
Domain
backend, observability
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.