export_byte_cap_exceeded
The packaged download exceeds the BYTE cap of that artifact type. It counts weight, not documents, so a small batch of very heavy documents —illustrated template, attachments— reaches it too. The `subcode` says when it was rejected: `before_writing`, when the estimated weight already exceeded it and NOTHING was written, or `while_writing`, when the real weight exceeded it mid-packaging and the partial file was discarded.
| Code | Type | HTTP | Category |
|---|---|---|---|
export_byte_cap_exceeded | invalid_request_error | 413 | Exports |
Cause
The packaged download exceeds the BYTE cap of that artifact type. It counts weight, not documents, so a small batch of very heavy documents —illustrated template, attachments— reaches it too. The subcode says when it was rejected: before_writing, when the estimated weight already exceeded it and NOTHING was written, or while_writing, when the real weight exceeded it mid-packaging and the partial file was discarded.
What to do
Ask for fewer documents per call; the weight per document is not something the request controls, so the only adjustment that works is shrinking the batch. A truncated archive is never delivered: if you get this error, there is no half-finished download to recover. If the volume is legitimate and sustained, request an increase of the cap for your company.