{"version":"2.1.318","anchor":"usage-limit-grace-resend-class-added","canonical_anchor":"usage-limit-grace-resend-class-added","heading":"One retry after a usage-limit rejection, controlled by a remote switch","tier":"notice","area":"Usage & Limits","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/usage-limit-grace-resend-class-added","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### One retry after a usage-limit rejection, controlled by a remote switch\n\nClaude Code has code to resend a request once after it is rejected for hitting a five-hour or seven-day usage limit, behind a remote switch\n\n**Unclear.** It is not stated how the remote switch controls the retry, so whether the retry happens for anyone is unclear.\n\n**What**\n\nClaude Code now contains code that resends a request one time after the server turns it down because a usage limit was reached. It applies only when the rejection names the five-hour or the seven-day limit. The behaviour is tied to a switch that the server can set, which falls back to false when the server sends nothing.\n\n**Why**\n\nThis points towards a short grace period, where a request that just crossed a usage limit gets one more attempt instead of failing straight away.\n\n- Flag `tengu_glittery_tower_killswitch`: Not enough to say (read for one account on one subscription tier against v2.1.318; this account: no value returned, anonymous baseline: no value returned, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}