Detected issues

Opt-in error detection from real visitor sessions — grouped, trended, and gated behind a human review queue.

Detected issues catches the bugs nobody reports: opt in, and Rebase auto-collects uncaught exceptions and unhandled promise rejections from everyone browsing your site — including the users who would never click "report".

Off by default, opt-in per project

Proactive detection is off until an owner turns it on, per project, in Settings. Once enabled it runs on every visitor session.

A review queue, not ticket spam

Detected errors land in a staged queue — not your ticket list, and not your tracker. Nothing becomes a ticket until a human promotes it. Your tracker only ever sees what you chose to send it.

Grouped, counted, trended

Errors are fingerprinted and collapsed, so the queue stays a list of distinct problems:

• One row per distinct error, with an occurrence count, first and last seen, and how many sessions were affected.
• A 14-day daily trend per group, so you can see whether it's growing.
• Grouped across pages: the same error on five routes is one row listing all five paths — not five rows.
• The trigger: each detected issue records the last user action before the crash — the click that set it off.

Recurring errors get their stacks symbolicated from the second occurrence, matched against your repo to surface a suspected file and line. This needs your sourcemaps to be reachable — see Source attribution.

Promote, snooze, mute

• Promote — one click creates a real ticket that flows through the entire pipeline: AI triage, source attribution, tracker issue. Promoting the same candidate twice returns the same ticket.
• Snooze — hides an error until it happens 10 more times.
• Mute — silences it permanently.
• Dismissed items clean themselves up after 30 days.

Flood-proof by design

An error storm can't take you down — or drown you:

Detected issues vs. reported bugs

A reported bug starts from a person who clicked capture; a detected issue starts from a crash in a session where nobody did. Both end up as the same kind of ticket once promoted — full capture context, triage, tracker sync. The review queue is the only difference: machines propose, you decide.