{"version":"2.1.251","anchor":"automatic-artifact-replies-report-usage-limits-distinctly","canonical_anchor":"automatic-artifact-replies-report-usage-limits-distinctly","heading":"Automatic artifact replies report usage limits distinctly","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/automatic-artifact-replies-report-usage-limits-distinctly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Automatic artifact replies report usage limits distinctly\n\nAutomatic artifact replies now report a usage limit instead of retrying blindly.\n\n**What**\n\nThe background job that composes automatic replies and edits on artifacts used to fold every API error into one generic failure and retry. It now recognises a usage-limit response and reports it as its own declined outcome instead.\n\n**Details**\n\n- The usage-limited case surfaces as a declined status rather than a generic compose failure headed for retry.\n- Other API errors keep the previous generic-error-and-retry behaviour.\n\n**Evidence**\n\n`compose_usage_limited`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}