Skip to content

Google Docs sync cannot page past the first batch (no server-side order/cursor) #57

Description

@YellowSnnowmann

Surfaced by CodeRabbit on #48 (providers/google_docs.rs ~L78-89). Pre-existing — engine original providers/google_docs.rs:88 sends the same {"query": "", "max_results": N}; ported unchanged.

GOOGLEDOCS_SEARCH_DOCUMENTS supports order_by; the request sends neither an order nor state.cursor as a modification-time filter, and max_pages is 1. Documents outside the first batch are unreachable; the orchestrator's dedup only filters the repeated response after fetching it.

Fix: deterministic modification-time ordering + apply the cursor as a filter; if the action lacks a mod-time filter, document the limitation explicitly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions