{"version":"2.1.323","anchor":"not-forwarded-error-gains-container-limit-reason","canonical_anchor":"not-forwarded-error-gains-container-limit-reason","heading":"A not-forwarded error can now say a container limit was the reason","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/not-forwarded-error-gains-container-limit-reason","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### A not-forwarded error can now say a container limit was the reason\n\nThe error for a message that was not forwarded can now carry a container_limit reason; unknown reasons are ignored\n\n**Unclear.** When this error is sent and what a user sees when it carries the new reason is not stated.\n\n**What**\n\nThe error Claude Code receives when a message was not forwarded can now include a reason. The only reason it accepts is `container_limit`. Any other value is ignored. Before, the error carried only a type and a message.\n\n**Why**\n\nA refusal caused by a container limit can now be told apart from other forwarding failures.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}