{% extends "_layout.html" %} {% set title = "Upload too large" %} {% set status = "413 Content Too Large" %} {% set description = "Any request body over its endpoint’s cap, not only an upload." %} {% block main %}
Too much was sent — most often a job’s archives, which together may not exceed limits.max_upload_bytes, refused at the upload grant before any bytes move. The name reads narrower than the rule: it also covers any request body over its endpoint’s cap.
size_bytes and any sent before it — with limits.max_upload_bytes in GET /v1. limit is present only for that case; a body over its endpoint’s cap carries none.An untyped answer is expected here. This refusal is often produced below the
request handler — by routing, the framework or a proxy — and then it arrives as the web
server’s own page, not as application/problem+json, and has no type
at all. Treat a non-problem+json 413 exactly as you would this type.
{
"type": "https://sc.example.com/server-errors/upload-too-large",
"title": "Upload too large",
"status": 413,
"detail": "...",
"instance": "/v1/jobs/01J9...",
"limit": "max_upload_bytes", // only over max_upload_bytes
"trace_id": "4bf92f3577b34da6a3ce929d0e0e4736"
}
| Member | ||
|---|---|---|
limit | optional | max_upload_bytes, where the job’s archives together went over it, and absent where a request body went over its endpoint’s cap. |
trace_id | optional | The request’s W3C trace id. Quote it in a support request. |
detail is prose and may be reworded at any time. Branch on type, and read the members above for the specifics — never parse detail.
POST /v1/jobs/{id}/upload-grant |
size_bytes takes the job’s archives together over limits.max_upload_bytes, with limit. The grant fixes the size, so an oversized archive is refused before it is sent. |
| any endpoint | A request body over that endpoint’s cap, with no limit. |
archive-rejected is an archive within the size limit that broke another rule once opened.