Your Compute job returned partial results
What to do when a result is incomplete or a download stops early, and how to tell what is missing.
Check coverage before using the output
Your result contains only part of the expected work. Read the result summary and any failure or exception records before using the accepted rows. Keep the original job or batch reference.
Partial output can be useful without being complete. A page of results may also be one part of a paginated response, rather than evidence that other items failed.
Identify what is missing
More pages are available: follow the returned cursor using the same authorized result read. Do not invent cursor values or infer missing items from output order.
The job is still running: retain the available immutable parts and read current job state. Do not label them as a complete terminal bundle.
Items failed or abstained: inspect the reason and item identity. An abstention is different from a fabricated answer and may require human review.
The job is terminal but coverage is unclear: stop downstream use that requires completeness. Ask Lithi to reconcile the missing coverage before repeating work.
Join results by the stable customer item identifiers used by the workflow, not by array position. Keep private mappings and source records outside support messages.
For example, if you expected eight items and can account for only seven, check the returned pages and recorded outcomes for the missing ID before treating the result as complete. The first test shows a small fictional fixture with accepted, invalid and abstained items.
Choose what to do with the remainder
Check whether the accepted subset meets your actual purpose. Review disagreements and high-impact items before relying on it. A valid digest does not prove every interpretation is correct.
For genuinely new work on selected failed or missing items, review that exact subset, input version, quote, and approval. Do not resubmit the entire batch by default. Accepted output, chargeable usage, and payment remain separate facts under the applicable terms.
Confirm or stop
Success means you can account for the expected items and know which output is usable, incomplete, or needs review. Stop if coverage cannot be established.
Use Contact Lithi with the job reference, expected and observed counts, safe outcome codes, and client version. Do not include full records, private item mappings, or signed download URLs.