Table draft limits

Plan source selections, field counts, capture sizes, and concurrent drafts.

Document-to-table drafts have bounded source and field sizes. These limits protect the completeness of a reviewable candidate and are separate from general provider transfer or managed upload limits.

Workspace policies and App-specific upload rules can impose additional limits. A file that passed upload can still be ineligible for a larger extraction batch. Check the stage-specific error instead of assuming the upload must have failed.

Choose a manageable source set

Select related documents that fit the same intended table meaning. A new table without supplied definitions needs one selected schema-reference document. Updating a saved table needs an explicit target and the current schema and data revisions.

Splitting a large set can help keep the review understandable, but separate drafts capture their sources independently. Do not present multiple batches as one simultaneous snapshot.

Draft lifecycle

A draft can be capturing, extracting, ready for review, applied, failed, or cancelled. A replacement preview does not discard the prior review before the replacement is ready. Successfully superseded previews move out of the active set rather than occupying the active-draft allowance indefinitely.

Do not start repeated drafts to recover an uncertain request. Use the existing intent's recovery path and inspect the saved draft or acceptance receipt. That avoids unnecessary generation and helps preserve the relationship between the review you inspected and the table you accepted.

See document extraction, refresh conflicts, and review limits.