> ## Documentation Index
>
> Fetch the complete documentation index at: https://lithi.ai/llms.txt
>
> Use this file to discover all available pages before exploring further.

## Some items came back and some did not

The job reported PARTIAL, or you have fewer output rows than input items. You need to know which items are missing, and why.

Accepted results are preserved. A partial job never discards the work that succeeded.

## Check for the manifest before anything else

The result bundle ends with result-manifest.json, and it is written last. It is the only complete-bundle marker.

If the manifest is absent, you are reading a partial cursor, not a final result. The presence of part files means nothing on its own. Read the job status again.

If the manifest is present, it binds every file, count, schema, release and retention rule in the bundle. Reconcile against its counters, not against your own assumptions.

## Then do this

1. Match the item identity field you declared on your input against the lithi_status column on each output row.
2. Read failures for typed failures and refusals, abstentions for items the workflow declined to judge, and disagreements for preserved verifier disagreements.
3. Compare the totals in metrics.json against your input item count. The three buckets plus the accepted rows should account for everything.
4. Check the completion policy on your workflow profile. It decides whether a run with failures ends PARTIAL or FAILED.

Then rerun only what you need. Submit the missing item identities as their own input, against their own quote.

## What not to repeat

Do not rerun the whole batch to recover a handful of items. The accepted results are already yours, and a full rerun pays for them a second time.

Do not treat a downloaded part file as the answer. Without the manifest you cannot know the set is complete, and a truncated part file reads exactly like a complete one.

Do not delete the original bundle before you have reconciled. The failure detail lives there.

## Get help safely

Send the job reference, the request ID from your result call, and the operation name. Add your client version, the contract release, the item counts expected and received, and the time.

Leave out payloads, output rows, key values, signed URLs, and banking information.

Read more about [partials and cursors](/docs/compute/results/partials-and-cursors) and [failures, abstentions and disagreements](/docs/compute/results/failures-abstentions-disagreements).