{"version":"2.1.251","anchor":"usage-limits-reported-distinctly-from-generic-failures","canonical_anchor":"usage-limits-reported-distinctly-from-generic-failures","heading":"Usage limits reported distinctly from generic failures","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/usage-limits-reported-distinctly-from-generic-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Usage limits reported distinctly from generic failures\n\nBackground composition now reports hitting a usage limit rather than a generic failure.\n\n**What**\n\nWhen a background composition step fails because of a usage limit, it is now reported as declined with the reason `usage_limited`, rather than being lumped in with every other failure as a generic compose failure.\n\n**Evidence**\n\n`reason: \"usage_limited\"`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}