fix(sidecar): resume Gmail history past page cap when pages are deduped - #679
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
…ed (#667) When Gmail history spans more than MAX_HISTORY_PAGES (3) and pages 1–3 are fully deduped, truncated=true froze the cursor forever and page 4+ messages were never ingested — silent data loss during mail bursts. Persist history_page_token in sidecar_state (migration 32) and pass it to listNewMessageIds so the next poll resumes from the dangling pageToken instead of re-fetching already-deduped pages. 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 | 15aa459 | Commit Preview URL Branch Preview URL |
Aug 09 2026, 11:06 AM |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
agentic-inbox | 15aa459 | Aug 09 2026, 11:07 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_page_tokeninsidecar_state(migration 32) when Gmail history listing hits the 3-page cap with more pages pending.listNewMessageIdson the next poll so the poller resumes from the danglingpageTokeninstead of re-fetching already-deduped pages 1–3.Why
When Gmail history spans more than
MAX_HISTORY_PAGES(3) and pages 1–3 are fully deduped,truncated=truefroze the cursor forever and page 4+ messages were never ingested — silent mail loss during bursts for Workspace sidecar mailboxes.Test plan
npm run typecheckpasses locallynpm testpasses locally (59 tests in workspace-poll, gmail-client, sidecar-state)history_page_tokenand converges on poll 2Notes for reviewer
Rule 6 cursor-advance logic now has a third branch: when truncated with a dangling
nextPageTokenand the current window is exhausted (all deduped or empty), persist the resume token without advancinghistory_cursor.