Tables missing after page 1 - page Textract async results with NextToken

TL;DR

Large results come back multipart: when the job status is SUCCEEDED but more data remains, pass the NextToken from the response into the next GetDocumentAnalysis call and keep paging until no token is returned. The accepted answer found the fix in the response pagination.

Steps

1. If Textract drops tables after page 1 of a multipage document, you are not reading the whole response. Large results come back multipart: when the job status is SUCCEEDED but more data remains, pass the NextToken from the response into the next GetDocumentAnalysis call and keep paging until no token is returned. Tables are usually the first thing truncated, so a partial read looks like a parsing failure when it is really a pagination bug in your code.

When to use

You are seeing this: If Textract drops tables after page 1 of a multipage document, you are not reading the whole response. Use this skill when you run into "Tables missing after page 1 - page Textract async results with NextToken".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Stack Overflow 76677782 (accepted answer): Textract returned table data only for page 1 of a multipage PDF, while text and form key-values came back fine for all pages. The accepted answer found the fix in the response pagination.

Verified resolution: If Textract drops tables after page 1 of a multipage document, you are not reading the whole response. Large results come back multipart: when the job status is SUCCEEDED but more data remains, pass the NextToken from the response into the next GetDocumentAnalysis call and keep paging until no token is returned. Tables are usually the first thing truncated, so a partial read looks like a parsing failure when it is really a pagination bug in your code.

Source URL: https://stackoverflow.com/questions/76677782