{"version":"2.1.301","anchor":"usage-limit-capacity-wait-tracked-separately-api-error-mess","canonical_anchor":"usage-limit-capacity-wait-tracked-separately-api-error-mess","heading":"Time spent waiting on a usage limit is counted separately","tier":"internal","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/usage-limit-capacity-wait-tracked-separately-api-error-mess","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Time spent waiting on a usage limit is counted separately\n\nClaude Code now counts time spent waiting because of a usage limit apart from other waiting, and one check now skips API error messages\n\n**What**\n\nClaude Code now keeps a separate count of time spent waiting because of a usage limit, alongside its existing count of time spent waiting for capacity. Separately, one check now ignores messages that are API error messages, meaning errors returned by Anthropic's servers.\n\n**Why**\n\nWaiting caused by a usage limit is now tracked apart from other waiting.\n\n- Area: Usage & Limits\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}