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

## Your input was refused before admission

Your quote or run came back with an input failure. No items were processed, and the refusal names both a reason and a next action.

Read the reason literally. Input refusals are precise, and the wording tells you which of three problems you have.

## Read the exact failure first

- Format failures mean the declared format does not match the bytes, or that format is not supported by this workflow.
- Item failures mean the item identity field you declared is missing, duplicated, or unreadable, so items cannot be counted or tracked individually.
- Byte failures mean the content digest does not match the snapshot you referenced, or a single item exceeds the profile bounds.

Check the failure against the workflow descriptor. It states the supported formats and the maximum item count for that workflow, and your quote repeats the same limit.

## Then do this

Inspect and convert on your own machine before you resubmit. Local inspection needs no admitted job and tells you the real shape of your data.

If a single item does not fit the profile bounds, four routes are supported. Use a registered deterministic sectioning strategy, a declared preprocessing stage, an approved larger profile, or a typed refusal you accept.

If the shape is unfamiliar, submit a small first test of a few items. Confirm the output columns and the failure handling, then run the full set.

For byte failures, take a fresh snapshot and quote against its new digest. Do not point an old snapshot reference at new content.

## What not to repeat

Renaming a file never changes what the bytes are, and never bypasses a policy. A spreadsheet renamed to a data extension still fails the format check, one step later and with less useful wording.

Never truncate required evidence to make an item fit. Never remove schema or rubric instructions, and never swap the model. Each of those changes what your result means while leaving it looking valid.

## Get help safely

Send the request ID, the operation name, and the safe error code. Add your client version, the contract release, and the time with its time zone.

Describe the format and approximate size in words. Never attach the file, a payload sample, a key, a signed URL, or banking information.

Read more in [how to inspect input locally](/docs/compute/inputs/local-inspection) and [the profile bounds a single item must fit](/docs/compute/workflows/gemma-bounds).