Skip to content

Report writes that keep failing to Sentry - #1918

Closed
joepio wants to merge 2 commits into
developfrom
claude/project-thread-u8vgm0-report-failing-commits
Closed

joepio wants to merge 2 commits into
developfrom
claude/project-thread-u8vgm0-report-failing-commits

Conversation

@joepio

@joepio joepio commented Sep 29, 2026

Copy link
Copy Markdown
Member

What

Before: a write that the server kept refusing (for instance "Parent of … not found" when a server never received a drive's root) was retried in the background and only ever showed up in the browser console. Sentry saw nothing, so a drive that could not sync was invisible to us.

After: when the same queued write has failed four drains in a row, one Sentry warning "Commit keeps failing" is sent per failure streak. It is grouped by server and error text with identifiers removed, and carries the subject and failure count. The write keeps retrying exactly as before; nothing changes for the user.

How

LocalOutbox gets an onRepeatedFailure hook that fires once when an entry's failure count reaches REPORT_AFTER_FAILURES. Store emits it as StoreEvents.CommitRepeatedlyFailing, and reportRepeatedCommitFailures in helpers/sentry.ts (wired in App.tsx) forwards it to Sentry when Sentry is enabled. Tests: the outbox reports once at the threshold without blocking or dropping the entry, and the Sentry fingerprint ignores resource ids. Lint passes. Not tried against a live Sentry project.


Generated by Claude Code

joepio commented Oct 5, 2026

Copy link
Copy Markdown
Member Author

Landed on develop in the combined batch #2060 (95707c0), tested together in one full run. Closing as included.


Generated by Claude Code

@joepio joepio closed this Oct 5, 2026
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