{"version":"2.1.239","anchor":"spend-limits-are-now-recognised-as-rate-limits","canonical_anchor":"spend-limits-are-now-recognised-as-rate-limits","heading":"Spend limits are now recognised as rate limits","tier":"notice","area":"Rate Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/spend-limits-are-now-recognised-as-rate-limits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Spend limits are now recognised as rate limits\n\nHitting a service spend limit is now recognised as a usage limit rather than a vague error.\n\n**What**\n\nA 429 response is treated as a usage-limit condition in more cases: when the body mentions a reached service spend limit, when a response header names a known limit type, or when the error message matches a known type.\n\n**Details**\n\n- Triggered by the body text `service_spend_limit_reached`.\n- Unconditional part of 429 handling.\n\n**Evidence**\n\n`service_spend_limit_reached`\n\n- Area: Rate Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}