Skip to content

docs(firestore-incremental-capture): document Cloud Tasks max document size limit#1103

Open
cabljac wants to merge 1 commit into
mainfrom
docs/issue-607-task-size
Open

docs(firestore-incremental-capture): document Cloud Tasks max document size limit#1103
cabljac wants to merge 1 commit into
mainfrom
docs/issue-607-task-size

Conversation

@cabljac

@cabljac cabljac commented Jul 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

Fixes the confusion reported in #607, where writes to the extension's captured collection fail with Error: Task size too large.

The extension syncs every Firestore write by enqueueing a Cloud Task that carries both the before and after state of the changed document. Cloud Tasks enforces a maximum task size of 100KB, so writes to large documents (Firestore allows up to 1 MiB) exceed the limit, fail to enqueue, and are silently not captured to BigQuery. This is a known limitation of the Cloud Tasks transport rather than a bug, so this PR documents it clearly.

Changes

  • Add a Known limitations section to PREINSTALL.md and README.md explaining:
    • why the Error: Task size too large error happens (both document states plus overhead in a single 100KB task),
    • that the affected change is not captured/restorable,
    • practical guidance: keep documents small (~50KB), split large documents, offload large fields to Cloud Storage, or use native PITR / Scheduled Backups for larger documents.
  • Bump extension version to 0.0.13 and update CHANGELOG.md.

Docs only - no behavior change.

Closes #607

@cabljac cabljac marked this pull request as ready for review July 2, 2026 08:36
…t size limit

Adds a Known limitations section to PREINSTALL.md and README.md
explaining that each Firestore write is synced via a Cloud Task that
carries both the before and after document state, and that Cloud Tasks
enforces a 100KB maximum task size. Documents whose combined state
exceeds this limit fail to enqueue with 'Error: Task size too large'
and are not captured to BigQuery.

Includes guidance on keeping documents small, splitting large documents,
offloading large fields to Cloud Storage, and using native PITR or
Scheduled Backups for larger documents.

Bumps version to 0.0.13 and updates the changelog.
@cabljac cabljac force-pushed the docs/issue-607-task-size branch from 0b36af6 to 85374fd Compare July 2, 2026 10:15
@cabljac cabljac requested a review from CorieW July 2, 2026 13:13

@CorieW CorieW left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incremental backups - Task Size too large

2 participants