{"version":"2.1.221","anchor":"spend-limit-message-distinguishes-an-org-spend-cap","canonical_anchor":"spend-limit-message-distinguishes-an-org-spend-cap","heading":"Spend-limit message distinguishes an org spend cap","tier":"notice","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/spend-limit-message-distinguishes-an-org-spend-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Spend-limit message distinguishes an org spend cap\n\nHitting a spend cap now says whether it's your individual limit rather than always the org's.\n\n**What**\n\nWhen the API reports overageDisabledReason \"org_spend_cap_reached\", the limit banner names your individual spend limit instead of always naming the org's monthly limit.\n\n**Details**\n\n- the banner reads \"You've hit your individual spend limit\" for that reason\n- the rejected-overage branch uses \"individual usage limit\"\n- both phrases are new in this build; other reasons keep the org monthly wording\n\n**Evidence**\n\n`individual spend limit`\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}