feat: improve UX during repairs#1580
Merged
tyler-dane merged 7 commits intomainfrom Mar 28, 2026
Merged
Conversation
tyler-dane
added a commit
to Muhammad-Nur-Alamsyah-Anwar/compass
that referenced
this pull request
Mar 30, 2026
* feat: added repair ux * feat(backend): add repair logic * fix: address comments * chore: cleanup backend errors * refactor: convert state to 'operation' message from webhooks for simplicity * fix(web): correct error msg * fix(web): make stop repair conditional
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Closes #1576
Note
Medium Risk
Touches Google Calendar sync/repair flows across backend websocket payloads and frontend state/UI, so regressions could affect sync status reporting and user remediation behavior. Changes are guarded by tests but span multiple layers (API error parsing, websocket events, Redux, and UI).
Overview
Improves Google Calendar repair UX by making repair vs incremental sync explicit end-to-end. Websocket
IMPORT_GCAL_ENDpayloads now include anoperation(REPAIR/INCREMENTAL), and both backend repair/incremental sync emit this consistently.Adds smarter repair failure handling and messaging. Backend detects Google rate-limit/quota errors to return a friendlier message, and treats revoked/invalid tokens during repair by pruning Google data + emitting
GOOGLE_REVOKEDinstead of a generic repair error.Updates web UI to reflect active repairs and show actionable feedback. Frontend tracks
isRepairing, shows a dedicated "Repairing…" state/spinner, clears repair state on repair completion/revoke, and shows a single de-duped toast for repair failures (but not for incremental errors).Written by Cursor Bugbot for commit 6c374d8. This will update automatically on new commits. Configure here.