{"version":"2.1.323","anchor":"new-api-wait-telemetry-label-and-control-response-error-code","canonical_anchor":"new-api-wait-telemetry-label-and-control-response-error-code","heading":"Overload waits get their own label, and some SDK error replies carry a code","tier":"internal","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/new-api-wait-telemetry-label-and-control-response-error-code","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Overload waits get their own label, and some SDK error replies carry a code\n\nClaude Code now names time spent waiting on an overloaded API, and some error replies to SDK requests include an error code\n\n**What**\n\nTwo separate additions:\n\n- Overload waits: Claude Code's list of named API operations gained one for waiting while the API is overloaded.\n\n- Error codes: when a program driving Claude Code through the SDK (the toolkit for controlling Claude Code from code) sends a control request and gets an error back, that reply now includes an `error_code` field for one particular kind of error.\n\n**Why**\n\nThe overload label points to Claude Code handling overloaded-API waits as their own step. Programs built on the SDK can read `error_code` to tell that kind of error apart from others.\n\n- Area: SDK\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}