{"version":"2.1.304","anchor":"api-refusal-trigger-added-to-a-trigger-set","canonical_anchor":"api-refusal-trigger-added-to-a-trigger-set","heading":"API refusals now count as a trigger alongside retries and successes","tier":"internal","area":"API","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/api-refusal-trigger-added-to-a-trigger-set","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### API refusals now count as a trigger alongside retries and successes\n\nA check that already reacted to accelerated retries and successful API responses now also reacts to API refusals\n\n**Unclear.** It is not clear what this check controls, so what a refusal now changes for a user is unknown.\n\n**What**\n\nClaude Code has an internal check that reacts to certain events when it talks to the API, the service that runs the model. That check already matched an accelerated retry and a successful response. It now also matches a refusal, meaning a request the API declined to answer.\n\n**Why**\n\nRefusals from the API are now handled the same way as those other two events wherever this check is used.\n\n- Area: API\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}