{"version":"2.1.228","anchor":"oversized-media-in-a-request-is-now-its-own-rejection-class","canonical_anchor":"oversized-media-in-a-request-is-now-its-own-rejection-class","heading":"Oversized media in a request is now its own rejection class","tier":"notice","area":"API Errors","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/oversized-media-in-a-request-is-now-its-own-rejection-class","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Oversized media in a request is now its own rejection class\n\nSending too many images or documents now reports a clear media-budget error and retries without them.\n\n**What**\n\nA 400 whose message mentions too much media is classified as a media budget failure; the retry path strips both document and image blocks, and the error surfaces to you as `media_budget_exceeded`. Previously this was matched ad hoc against two literal substrings.\n\n**Details**\n\n- The surrounding classifiers now take a message string rather than an Error object.\n\n**Evidence**\n\n`media_budget_exceeded`\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}