Skip to content

fix(conversations): stop loading after reaching the pagination cap - #120751

Open
fallintoplace wants to merge 1 commit into
getsentry:masterfrom
fallintoplace:fix/conversation-pagination-cap
Open

fix(conversations): stop loading after reaching the pagination cap#120751
fallintoplace wants to merge 1 commit into
getsentry:masterfrom
fallintoplace:fix/conversation-pagination-cap

Conversation

@fallintoplace

Copy link
Copy Markdown

Summary

  • use the pagination cap when deciding whether conversation details are still loading
  • stop reporting a loading state after ten pages even when the API returns another cursor
  • cover the capped case with ten paginated responses

Why

Conversation details automatically fetch at most ten pages. Previously, the returned loading state used the raw hasNextPage value, so conversations with more than 10,000 spans stayed in a loading state forever after page ten.

Testing

  • pnpm exec jest static/app/views/explore/conversations/hooks/useConversation.spec.tsx --runInBand
  • pnpm exec oxfmt --check static/app/views/explore/conversations/hooks/useConversation.tsx static/app/views/explore/conversations/hooks/useConversation.spec.tsx
  • pnpm exec eslint static/app/views/explore/conversations/hooks/useConversation.tsx static/app/views/explore/conversations/hooks/useConversation.spec.tsx

@fallintoplace
fallintoplace requested a review from a team as a code owner July 28, 2026 16:52
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant