{"version":"2.1.317","anchor":"cloud-gateway-guidance-relay-bedrock-input-is-too-long","canonical_anchor":"cloud-gateway-guidance-relay-bedrock-input-is-too-long","heading":"Gateway guidance now says to pass Bedrock's \"Input is too long.\" error through unchanged","tier":"notice","area":"Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/cloud-gateway-guidance-relay-bedrock-input-is-too-long","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Gateway guidance now says to pass Bedrock's \"Input is too long.\" error through unchanged\n\nClaude Code's built-in gateway guide says a Bedrock 400 error reading exactly \"Input is too long.\" must reach Claude Code unchanged\n\n**What**\n\nClaude Code includes a guide for people writing a gateway, a server that sits between Claude Code and the model provider. The guide tells gateway authors to clean up (sanitize) error messages before passing them on, with exceptions for messages that must reach Claude Code word for word.\n\nThere used to be one exception: a 400 or 413 error saying `prompt is too long`. There are now two. A 400 error from Amazon Bedrock whose entire message is `Input is too long.` must also be passed through unchanged.\n\n**Why**\n\nClaude Code recovers from this Bedrock error by dropping older images from the conversation and then compacting it, which means condensing earlier messages to save space. It recognises the error only by its exact text, so a gateway that rewrites the message stops that recovery from happening.\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}