Archive Criteria

1. Single-event fluke

Issues with exactly one occurrence, one or zero users, that never recurred.

• Signals: events ≤ 2, users ≤ 1, firstSeen and lastSeen within ~1 hour of each other, no recurrence in 30+ days.
• Examples: isolated TypeErrors in random anonymous functions, one-off ReferenceError from a script that no longer runs.
• Reason: Single-event fluke — N event(s), N user(s), no recurrence.
• Caution: if firstSeen is within the last 7 days and the title looks like a real bug (“TypeError” in our app code), prefer skip and let it bake.

2. Test / synthetic / security-research

Events generated by smoke tests, customer security audits, or internal QA probes — not real user traffic.

• Signals: title contains any of: test, smoke test, verify test, XSS, SSRF, SSTI, CSP test, <script, <img src=x, {{7*7}}, data uri injection, security-event-injection.
• Often includes a trailing epoch-millisecond timestamp. Volume is typically ≤ 5 events.
• Examples:
  • Error: Sentry verify test
  • Attachment SSRF test
  • <img src=x onerror=...>
  • Error: CSP test <timestamp>
• Reason: Test/synthetic event — synthetic traffic from smoke test or security probe.

3. Wrong-project / non-frontend errors

Errors that originate in customers’ own backends but get reported to sentry/javascript because of misconfigured DSNs or shared SDKs.

• Signals: title prefix is PrismaClientKnownRequestError, PrismaClientUnknownRequestError, HTTPException, AttributeError, ImportError, ProgrammingError, or ZodError with Python-shaped stacks.
• Culprit looks like a Python module path (e.g., dotted module.submodule.handler) or a backend middleware class.
• Examples:
  • PrismaClientKnownRequestError: (any)
  • AttributeError: 'dict' object has no attribute '<field>'
  • HTTPException with a Python dotted-module culprit
• Reason: Wrong project — non-frontend error mis-routed (Prisma/Python).

4. Customer-environment third-party library noise

Errors whose top in-app frame is in a third-party library that we depend on (or that customers’ apps depend on) — not in our code.

• Signals: top frame is under node_modules/ for a library name like echarts, mobx, html2canvas, react-dom (only when the error is React-internal and not our component), lodash, etc.
• Also: title references third-party globals injected by browser extensions or wallet providers.
• Examples:
  • TypeError: Cannot set properties of null (setting 'innerHTML') with top frame in echarts/lib/component/tooltip/...
  • Error: [MobX] minified error nr: <N> (mobx internals)
  • ReferenceError: Can't find variable: DarkReader
  • TypeError: undefined is not an object (evaluating 'window.ethereum.<prop>')
  • ReferenceError: html2canvas is not defined
• Reason: Third-party library noise — <library>; not actionable in our code.
• Caution: if the third-party frame is reached from our component code with our state, it might be a misuse on our side. Inspect the second frame down — if it’s our app/ code passing bad input, prefer skip.

5. Browser API / permission noise

Errors caused by browser APIs the user denied, browser quirks, or platform constraints we cannot work around.

• Signals: title contains:
  • NotAllowedError (clipboard, WebAuthn, permissions, 2FA)
  • OperationError: A request is already pending (WebAuthn pipeline)
  • SecurityError: Blocked a frame ... cross-origin
  • SecurityError: Failed to read a named property ... from 'Window'
  • Failed to execute 'writeText' on 'Clipboard'
  • WebGL not supported
  • NotReadableError, NotSupportedError: ... public key credentials
  • Could not establish connection. Receiving end does not exist.
  • A listener indicated an asynchronous response by returning true
  • Invalid call to runtime.sendMessage() (extension messaging)
  • IndexedDB ... Internal error opening backing store
  • An error occured reading the Blob argument to createImageBitmap
• Examples:
  • NotAllowedError: Failed to execute 'writeText' on 'Clipboard': Document is not focused.
  • OperationError: A request is already pending.
  • SecurityError: Blocked a frame with origin "<origin>" from accessing a cross-origin frame.
• Reason: Browser API permission noise — <specific API>; not actionable from our code.

6. Transient backend 5xx

Frontend errors that are downstream of intermittent backend failures already triaged elsewhere.

• Signals: title is InternalServerError: <METHOD> /api/0/..., ServiceUnavailableError: <METHOD> /..., or UndefinedResponseBodyError: <METHOD> /....
• Culprit is in app code that calls our API, but the root cause is a backend 5xx.
• Examples:
  • InternalServerError: GET /organizations/{orgSlug}/issues/{issueId}/ 500
  • ServiceUnavailableError: GET /<endpoint>/ 503
  • UndefinedResponseBodyError: GET /organizations/{orgSlug}/<endpoint>/ 200
• Reason: Transient backend 5xx — <method> <path>; backend transient, not a frontend bug.
• Caution: if a single 5xx is firing thousands of times per day to one specific endpoint, surface as needs-human — it may signal a real backend regression.

7. Network noise / Failed to fetch

Network failures to third-party hosts (analytics, CDNs, customer-side services) that we cannot fix from the frontend.

• Signals: title is TypeError: Failed to fetch (<host>) where <host> is not a Sentry-owned domain.
• Common patterns: well-known analytics endpoints, ad/marketing endpoints, customer-internal hostnames (often subdomains with random tokens), and one-off external CDNs.
• Examples:
  • TypeError: Failed to fetch (api2.amplitude.com) (well-known analytics)
  • TypeError: Failed to fetch (<customer-specific host>)
• Reason: Network noise — Failed to fetch from <host>; third-party network.
• Caution: Failed to fetch (sentry.io) from within a Sentry context could indicate a real outage. Check recency; if multiple users in the last hour, surface as needs-human.

8. Customer-environment proxy interference

Corporate proxies or content filters that intercept responses, returning HTML notification pages where JSON was expected.

• Signals: title is Error: 200 treated as error: ... or JSON parse error with response body containing <!DOCTYPE html> / <html> / proxy notice text (common products: McAfee, Forcepoint, Zscaler, Symantec).
• Examples:
  • Error: 200 treated as error: GET /organizations/{orgSlug}/projects/
• Reason: Customer-environment proxy interference — corporate proxy returned HTML for JSON request.

9. Zero-impact / unknown title

Issues with zero users impacted, very low event count, and no useful title (<unknown>, empty, or unparseable).

• Signals: users == 0 AND events ≤ 50 AND title is <unknown> or empty.
• Reason: Zero-impact — no users affected, low volume.
• Caution: unknown-title issues at high volume (events ≥ 1000) often hide real bugs that need a frame. Surface as needs-human rather than archive.

Negative criteria — do NOT archive

Even if an issue is high-volume or annoying, skip when any of these apply:

• Top in-app frame is in our application code (app/, static/, src/) — even if the error message is generic.
• Title contains ZodError with a stack pointing into our schema validation — likely a real schema mismatch we should fix.
• Title is a React internal error pointing at our component tree (useEffectEvent, hydration mismatch, render-time exceptions in our components).
• The issue was filed via “User Feedback” — someone took the time to report it.
• Volume jumped recently (e.g., 0 events 7 days ago → 1000 today) — looks like a regression.
• The error is Error: Should not already be working. from a React internal and it’s recurring across many users in our org — escalate.

When negative criteria fire, mark skip with a short note, e.g. Skip — top frame is our app/, looks actionable.

High-confidence vs. needs-human decision matrix