{"version":"2.1.319","anchor":"tasksget-oversize-answer-returns-a-dedicated-error","canonical_anchor":"tasksget-oversize-answer-returns-a-dedicated-error","heading":"Oversized task results now return their own error instead of a generic one","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/tasksget-oversize-answer-returns-a-dedicated-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Oversized task results now return their own error instead of a generic one\n\nWhen a tasks\/get answer is too big, too wide or nested too deeply, Claude Code now returns a dedicated error rather than the generic -32603 message\n\n**Unclear.** The code and wording of the new predefined error are not stated, so it is unclear what a program should now match on.\n\n**What**\n\n`tasks\/get` is a request another program can send to Claude Code to fetch the result of a task. Each answer has limits on its total size, on how many fields it has and on how deeply it is nested. When an answer goes over any of these limits, Claude Code now returns a specific, predefined error.\n\nBefore, every such case returned the generic error code -32603 with a message saying the answer was over a certain number of bytes.\n\n**Why**\n\nA program that reads these errors now gets a distinct error for oversized task results, so it can tell this case apart from other internal failures. A program that matched on the old -32603 message may need updating.\n\n- Area: SDK\n- Names: `tasks\/get`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}