fix(sidecar): persist Gmail history page token to prevent permanent mail loss - #685
Closed
cursor[bot] wants to merge 1 commit into
Closed
cursor[bot] wants to merge 1 commit into
cursor[bot] wants to merge 1 commit into
Conversation
…istory When listNewMessageIds hits the 3-page cap with more pages pending, the poller froze history_cursor but restarted pagination at page 1 on every subsequent poll. Once pages 1-3 were fully deduped the cursor could never advance and mail on page 4+ was permanently lost. Persist the dangling nextPageToken in sidecar_state (migration 32) and resume from it on the next poll. Clear the token when the listing completes or on history-gap re-anchor. Co-authored-by: schmug <schmug@users.noreply.github.com>
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
ais-hub | 0f8bee7 | Commit Preview URL Branch Preview URL |
Aug 13 2026, 11:10 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
agentic-inbox | 0f8bee7 | Aug 13 2026, 11:11 AM |
Owner
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
2 participants
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.
Summary
history.listnextPageTokeninsidecar_statewhen the 3-page history cap leaves more pages pendingWhy
When
listNewMessageIdshitsMAX_HISTORY_PAGES=3with a danglingnextPageToken, the poller correctly freezeshistory_cursorbut restarts pagination at page 1 on every subsequent poll. Once pages 1–3 are fully deduped, the cursor can never advance and mail on page 4+ is permanently lost — silent data loss for Workspace sidecar mailboxes during bursts.Test plan
npm testpasses locally (gmail-client, workspace-poll, sidecar-state — 60 tests)listNewMessageIdsreturnsresumePageTokenwhen truncatedNotes for reviewer
Cherry-pick of validated fix from prior bug-finding runs (
cursor/critical-bug-investigation-ba62). Same root cause identified on 2026-08-09 through 2026-08-12 scans; prior PR drafts never merged.