Skip to content

Filter retry exhaustion Sentry noise - #1373

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/por-20736-cursor-automated-triage-response-32bd
Draft

Filter retry exhaustion Sentry noise#1373
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/por-20736-cursor-automated-triage-response-32bd

Conversation

@cursor

@cursor cursor Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Added a shared Sentry ignore list for known retry/network-noise errors.
  • Applied it to server, edge, browser, and Trigger job Sentry initialization.
  • Covered the exact retryable error: max retries exceeded title and Sentry Replay retry exhaustion with a focused unit test.

Testing Criteria

  • yarn test src/utils/sentryIgnoreErrors.test.ts --runInBand
  • yarn prettier:check
  • yarn lint:check (passes with existing React hook/compiler warnings)
  • yarn tsc (fails only on existing src/icons/index.ts SVG module declaration errors)

Notes

  • Linear and Sentry MCP servers require authentication in this environment, so direct event details and ticket commenting were unavailable. The trigger payload was Triage, and repo Sentry config confirms this checkout uploads to Sentry project tasks.

Impact & Surface Area of Change

  • Sentry event filtering only. Review that legitimate application errors (for example Copilot API failures) are not filtered by the new retry/noise regexes.
Open in Web View Automation 

Co-authored-by: Neil Raina <makeitraina@users.noreply.github.com>
@linear-code

linear-code Bot commented Jul 3, 2026

Copy link
Copy Markdown

POR-20736

@vercel

vercel Bot commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tasks-app Ready Ready Preview, Comment Jul 3, 2026 3:22pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant