{"version":"2.1.318","anchor":"api-error-messages-max-output-tokens-many-image-pixel-limi","canonical_anchor":"api-error-messages-max-output-tokens-many-image-pixel-limi","heading":"More accurate error messages for image limits, output cutoffs and server errors","tier":"notice","area":"API Errors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/api-error-messages-max-output-tokens-many-image-pixel-limi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### More accurate error messages for image limits, output cutoffs and server errors\n\nErrors now cover output-token cutoffs, take the image pixel limit from the server, and drop the retry hint on one kind of server error\n\n**What**\n\nSeveral of the messages Claude Code shows when a request fails changed:\n\n- An error for hitting the output limit, `max_output_tokens`, now has its own message ending \"Try again.\" The output limit is the cap on how much Claude can write in one reply.\n\n- The error for an image that is too large in a request with many images now shows the pixel limit the server reports. It used to always say 2000px.\n\n- One kind of server error now shows only its message, without \"This is a server-side issue, usually temporary\".\n\n- A failure to refresh your sign-in now has its own version for when a time limit was reached.\n\n**Why**\n\nYou see error text that matches what actually happened, including the real image size limit.\n\n- Area: API Errors\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}