fix(sidecar): persist history page token to unblock truncated Gmail history - #677
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 | 2565328 | Commit Preview URL Branch Preview URL |
Aug 07 2026, 11:10 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
agentic-inbox | 2565328 | Aug 07 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_state.history_page_token(migration 32) when the 3-page cap leaves more pages pending.Why
When
listNewMessageIdshitsMAX_HISTORY_PAGES=3with more pages pending, the poller correctly frozehistory_cursorbut restarted 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 — a silent data-loss bug for sidecar mailboxes during bursts or catch-up after downtime.Test plan
npm testpasses locally (workspace-poll, gmail-client, sidecar-state — 60 tests)history_page_tokenis savedNotes for reviewer
Same fix has been drafted in prior automation runs (#667, #673) but never landed on main. This is the minimal migration + resume path; no change to the page cap itself.