# TOO_MANY_FILES_IN_CALL

Too many files in one call.

- **HTTP class:** 413
- **Retryable:** no

## What happened

The call carries more files than one call may: more than 72 with content when `finalize` is false (`{path, sha256}` references don't count there), or more than 30 entries in all when it is true (references count). Nothing was staged and no slot, key or counter was used; `error.max_files_per_call` is this call's cap.

## Fix

Resend with `finalize=false`, up to 72 files a call with the stylesheets in the first, keeping the returned `deploy_id`; then send the last 30 or fewer with `finalize=true`.

## What to tell the user

Nothing.

## Agent hint

The exact `error.hint` text; Carnival fills each `<…>` for the call.

```text
This call counts <n> files. Per call: at most 72 with content if finalize=false ({path, sha256} entries free), 30 in all if finalize=true. None were staged: resend with finalize=false, up to 72 a call, stylesheets first, keeping the returned deploy_id; the last 30 or fewer with finalize=true.
```

## Related

- [`PAYLOAD_TOO_LARGE`](https://carnival-staging.dev/docs/errors/PAYLOAD_TOO_LARGE.md): Too much data in one call.
- [`TOO_MANY_FILES`](https://carnival-staging.dev/docs/errors/TOO_MANY_FILES.md): The site has too many files.
- [`MISSING_CONTENT`](https://carnival-staging.dev/docs/errors/MISSING_CONTENT.md): Some files are missing.

All error codes: [error codes](https://carnival-staging.dev/docs/errors.md)